WO2023138382A1

WO2023138382A1 - Crash information collection method and apparatus

Info

Publication number: WO2023138382A1
Application number: PCT/CN2023/070575
Authority: WO
Inventors: 董彬; 钟炳鑫
Original assignee: 北京有竹居网络技术有限公司
Priority date: 2022-01-19
Filing date: 2023-01-05
Publication date: 2023-07-27
Also published as: CN116501520A

Abstract

Disclosed in the present application is a crash information collection method. For an instant application, a first functional module can capture crash stack information of the instant application, and the crash stack information is used for describing an operation fault of the instant application. The first functional module is a functional module in an operating system of a device carrying the instant application. After the first functional module captures the crash stack information, the crash stack information can be sent to the instant application. In view of the above, by using this solution, the crash stack information of the instant application can be obtained before the instant application processes the crash stack information. In this way, even if the instant application does not send the crash stack information to an application program running an instant framework, the application program running the instant framework can also receive the crash stack information, such that the application program running the instant framework can receive more crash stack information, thereby improving the stability of the instant application.

Description

A method and device for collecting crash information

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China on January 19, 2022, with application number 202210061363.0 and application title "A Method and Device for Collecting Crash Information", the entire contents of which are incorporated herein by reference.

technical field

The present application relates to the field of data processing, in particular to a method and device for collecting crash information.

Background technique

Free installation technology provides a complete virtual operating environment. Application programs that use installation-free technology can also be called "installation-free applications". The installation-free application does not need to be installed on the system, but it can also achieve the operation effect that can be achieved by installing the application.

In order to improve the stability of the installation-free application, it is necessary to monitor the operation failure of the installation-free application, so as to take further measures. However, the current solutions for monitoring operation failures of installation-free applications can only detect a part of operation failures, thereby reducing the stability of installation-free applications.

Therefore, there is an urgent need for a solution that can solve the above problems.

Contents of the invention

The technical problem to be solved in this application is how to improve the stability of installation-free applications, and provide a method and device for collecting crash information.

In the first aspect, the embodiment of the present application provides a crash information collection method, the method comprising:

Obtaining the crash stack information sent by the first functional module to the installation-free application, the crash stack information is used to describe the operation failure of the installation-free application, and the first functional module is a functional module in the operating system of the device carrying the installation-free application;

The crash stack information is sent to the application running the instant framework.

Optionally, the acquiring the crash stack information sent by the first functional module to the instant application includes:

Intercepting the crash stack information sent by the first functional module to the installation-free application.

Optionally, the intercepting the crash stack information sent by the first functional module to the installation-free application includes:

A hook function is used to intercept the first function for delivering the crash stack information.

Optionally, the installation-free application is a game application.

Optionally, the program code of the installation-free application is implemented by Java language, C language, C++ language, C# language, JavaScript language, ActionScript language, or lua language.

Receive the crash stack information sent by the first function module.

Optionally, the running application of the installation-free framework includes:

Platform applications running on said operating system.

In the second aspect, the embodiment of the present application provides a crash information collection device, the device includes:

An acquisition unit, configured to acquire crash stack information sent to the installation-free application by the first functional module, the crash stack information is used to describe the operation failure of the installation-free application, and the first functional module is a functional module in the operating system of the device carrying the installation-free application;

A sending unit, configured to send the crash stack information to the application running the installation-free framework.

Optionally, the acquisition unit is used for:

Optionally, the installation-free application is a game application.

Optionally, the acquisition unit is used for:

Receive the crash stack information sent by the first function module.

Platform applications running on said operating system.

In a third aspect, an embodiment of the present application provides a device, where the device includes a processor and a memory;

The processor is configured to execute instructions stored in the memory, so that the device executes the method described in any one of the above first aspects.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which is characterized by including instructions, and the instructions instruct a device to execute the method described in any one of the above first aspects.

In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a computer, causes the computer to execute the method described in any one of the above first aspects.

Compared with the prior art, the embodiment of the present application has the following advantages:

An embodiment of the present application provides a method for collecting crash information. For an installation-free application, the first functional module may capture the crash stack information of the installation-free application, and the crash stack information is used to describe the operation failure of the installation-free application. The first function module is a function module in the operating system of the device carrying the installation-free application. After the first function module captures the crash stack information, it may send the crash stack information to the installation-free application. In the embodiment of the present application, the crash stack information sent by the first functional module to the installation-free application may be obtained, and the crash stack information is further sent to the application running the installation-free framework. It can be seen that with this solution, the crash stack information of the installation-free application can be obtained before the installation-free application processes the crash stack information. In this way, even if the installation-free application does not send the crash stack information to the application running the installation-free framework, the application running the installation-free framework can also receive the crash stack information, so that the application running the installation-free framework can receive more crash stack information, thereby improving the stability of the installation-free application.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments or prior art. Obviously, the accompanying drawings in the following description are only some embodiments recorded in the application. For those of ordinary skill in the art, other accompanying drawings can also be obtained based on these drawings without creative work.

Fig. 1 is a schematic diagram provided by the embodiment of the present application;

FIG. 2 is a schematic flowchart of a method for collecting crash information provided by an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a crash information collection device provided in an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a device provided by an embodiment of the present application _.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiment of the application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiment of the application. Obviously, the described embodiments are only part of the embodiments of the application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

The platform application program can run on the operating system, the platform application program can run the installation-free framework, and the installation-free framework is used to implement the installation-free technology. In order to improve the stability of the installation-free application, it is necessary to monitor the operation failure of the installation-free application. Currently, the platform application can call an interface provided by the operating system to collect crash stack information of the free-to-install application, where the crash stack information is used to describe a running failure of the free-to-install application. However, it can be understood with reference to FIG. 1 , which is a schematic diagram provided by an embodiment of the present application. When the interface is used to collect the crash stack information of the installation-free application, the transmission path of the crash stack information is: function module 110--installation-free application 120-platform application 130. Wherein, the function module 110 is a function module for the operating system to capture crash stack information. However, in some scenarios, after receiving the crash stack information, the installation-free application 120 will execute corresponding processing measures based on the crash stack information, and will no longer send the crash stack information to the platform application 130 . As a result, the platform application 130 cannot collect all crash stack information. Correspondingly, it is not conducive to the stable operation of installation-free applications.

In order to solve the above problems, embodiments of the present application provide a method and device for collecting crash information.

Various non-limiting implementations of the present application will be described in detail below with reference to the accompanying drawings.

exemplary method

Referring to FIG. 2 , this figure is a schematic flowchart of a method for collecting crash information provided by an embodiment of the present application. The method provided in this embodiment can be applied to an operating system, and the operating system includes but is not limited to an Android (Android) system. The method can be implemented, for example, through the following steps S101-S102.

S101: Obtain crash stack information sent to the installation-free application by a first function module, the crash stack information is used to describe a running fault of the installation-free application, and the first function module is a function module in an operating system of a device carrying the installation-free application.

The embodiment of the present application does not specifically limit the installation-free application. In one example, the installation-free application is a game application. In the embodiment of the present application, the program code of the installation-free application may be realized by Java language, C language, or C++ language, which is not specifically limited in this embodiment of the present application. Of course, the program code of the installation-free application can also be implemented by C# language, JavaScript language, ActionScript language, or lua language, which is not specifically limited in this embodiment of the present application.

In this embodiment of the present application, the crash stack information of the installation-free application is used to describe the operation failure of the installation-free application. Faults during the running of the installation-free application may be captured by the operating system, specifically, by the first function module in the operating system. In other words, the first function module can capture the crash stack information. After the first function module captures the crash stack information of the installation-free application, it may send the crash stack information to the installation-free application. Wherein, the operating system mentioned here refers to the operating system of the device carrying the installation-free application.

If the operating system is an Android system, and the software code of the installation-free application is implemented by C language or C++ language, then the first functional module sends the crash stack information to the installation-free application. If the operating system is an Android system, and the software code of the installation-free application is implemented by the java language, then the first functional module sends the crash stack information to the installation-free application.

In an example, the first function module may use related functions to transmit the crash stack information to the installation-free application. The embodiment of the present application does not specifically limit the function for transferring the crash stack information.

In an example, during specific implementation of S101, the crash stack information sent by the first functional module to the installation-free application may be intercepted. Considering that a hook (hook) function can achieve the purpose of intercepting a certain function, therefore, in an implementation manner, the hook function may be used to intercept the first function used to transmit the crash stack information, so as to obtain the crash stack information.

In yet another example, when S101 is specifically implemented, the first functional module may be configured in advance, so that the first functional module not only sends the crash stack information to the installation-free application, but also sends the crash stack information to the second functional module of the operating system. The second functional module mentioned here refers to the functional module that executes S101-S102.

S102: Send the crash stack information to the application running the installation-free framework.

After the crash stack information is acquired, the crash stack information may be sent to the application program of the installation-free framework. The embodiment of the present application does not specifically limit the specific implementation manner of S102. In an example, related functions may be used to send the crash stack information to the application running the installation-free framework. It can be understood that the application program running the installation-free framework mentioned here refers to the platform application program running on the operating system.

As can be seen from the above description, using the solutions provided by the embodiments of the present application, before the installation-free application processes the crash stack information, the crash stack information of the installation-free application can be obtained, and the crash stack information can be sent to the platform application, thereby preventing the platform application from being unable to capture the crash stack information due to the processing of the crash stack information by the installation-free application. In other words, using the solution of the embodiment of the present application, even if the installation-free application does not send the crash stack information to the application running the installation-free framework, the application running the installation-free framework can still receive the crash stack information, so that the application running the installation-free framework can receive more crash stack information, which is conducive to the stable operation of the installation-free application.

exemplary device

Based on the methods provided in the above embodiments, the embodiments of the present application also provide a device, which will be described below with reference to the accompanying drawings.

Referring to FIG. 3 , this figure is a schematic structural diagram of a crash information collection device provided by an embodiment of the present application. For example, the apparatus 300 may specifically include: an acquiring unit 301 and a sending unit 302 .

The obtaining unit 301 is configured to obtain the crash stack information sent by the first functional module to the installation-free application, the crash stack information is used to describe the operation failure of the installation-free application, and the first functional module is a functional module in the operating system of the device carrying the installation-free application;

The sending unit 302 is configured to send the crash stack information to the application running the installation-free framework.

Optionally, the acquiring unit 301 is configured to:

Optionally, the installation-free application is a game application.

Optionally, the acquiring unit 301 is configured to:

Receive the crash stack information sent by the first function module.

Platform applications running on said operating system.

Since the device 300 is a device corresponding to the method provided by the above method embodiment, the specific implementation of each unit of the device 300 is based on the same idea as the above method embodiment, therefore, regarding the specific implementation of each unit of the device 300, you can refer to the description of the above method embodiment, and will not repeat them here.

The embodiment of the present application also provides a device, the device includes a processor and a memory;

The processor is configured to execute instructions stored in the memory, so that the device executes the method described in any one of the above method embodiments.

Referring to FIG. 4 , it shows a schematic structural diagram of an electronic device 400 suitable for implementing the embodiment of the present application. The electronic equipment in the embodiment of the present application may include, but not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDA (Personal Digital Assistant, personal digital assistant), PAD (portable android device, tablet computer), PMP (Portable Media Player, portable multimedia player), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TV (television, television sets), desktop computers, etc. The electronic device shown in FIG. 4 is only an example, and should not limit the functions and scope of use of this embodiment of the present application.

As shown in FIG. 4 , the electronic device 400 may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 401, which may perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage device 408 into a random access memory (RAM) 403. In the RAM 403, various programs and data necessary for the operation of the electronic device 400 are also stored. The processing device 401, the ROM 402, and the RAM 403 are connected to each other through a bus 404. An input/output (I/O) interface 405 is also connected to bus 404 .

Generally, the following devices can be connected to the I/O interface 405: an input device 406 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 407 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 408 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 409. The communication means 409 may allow the electronic device 400 to perform wireless or wired communication with other devices to exchange data. While FIG. 4 shows electronic device 400 having various means, it should be understood that implementing or having all of the means shown is not a requirement. More or fewer means may alternatively be implemented or provided.

In particular, according to the embodiments of the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments of the present application include a computer program product, which includes a computer program carried on a non-transitory computer readable medium, where the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 409 , or from storage means 408 , or from ROM 402 . When the computer program is executed by the processing device 401, the above-mentioned functions defined in the methods of the embodiments of the present application are performed.

The electronic device provided by the embodiment of the present application and the method for collecting crash information provided by the above-mentioned embodiment belong to the same inventive concept. The technical details not described in detail in this embodiment can be found in the above-mentioned embodiment, and this embodiment has the same beneficial effects as the above-mentioned embodiment.

An embodiment of the present application provides a computer-readable medium on which a computer program is stored, wherein when the program is executed by a processor, the method for collecting crash information as described in any of the above-mentioned embodiments is implemented.

It should be noted that the computer-readable medium mentioned above in this application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. A computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples of computer readable storage media may include, but are not limited to, electrical connections having one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In this application, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted by any appropriate medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

In some embodiments, the client and the server can communicate using any currently known or future-developed network protocols such as HTTP (HyperText Transfer Protocol, Hypertext Transfer Protocol), and can be interconnected with any form or medium of digital data communication (for example, a communication network). Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device, or may exist independently without being incorporated into the electronic device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device is made to execute the above-mentioned method for collecting crash information.

Computer program code for carrying out the operations of the present application may be written in one or more programming languages, or combinations thereof, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and conventional procedural programming languages—such as the “C” language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., through the Internet using an Internet service provider).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagram may represent a module, program segment, or portion of code that includes one or more executable instructions for implementing specified logical functions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block in the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or by combinations of special purpose hardware and computer instructions.

The units involved in the embodiments described in the present application may be implemented by means of software or by means of hardware. Wherein, the name of the unit/module does not constitute a limitation on the unit itself under certain circumstances, for example, the voice data collection module can also be described as a "data collection module".

The functions described herein above may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), System on Chips (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include one or more wire-based electrical connections, a portable computer disk, a hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

Other embodiments of the present application will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The present application intends to cover any modification, use or adaptation of the application, which follows the general principles of the application and includes common knowledge or conventional technical means in the technical field not disclosed in this disclosure. The specification and examples are to be considered exemplary only, with a true scope and spirit of the application indicated by the following claims.

It should be understood that the present application is not limited to the precise constructions which have been described above and shown in the accompanying drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims

The above descriptions are only preferred embodiments of the present application, and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included within the protection scope of the present application.

Claims

A crash information collection method, characterized in that the method comprises:

Obtaining the crash stack information sent by the first functional module to the installation-free application, the crash stack information is used to describe the operation failure of the installation-free application, and the first functional module is a functional module in the operating system of the device carrying the installation-free application;

The crash stack information is sent to the application running the instant framework.
The method according to claim 1, wherein the obtaining the crash stack information sent by the first functional module to the installation-free application includes:

Intercepting the crash stack information sent by the first functional module to the installation-free application.
The method according to claim 2, wherein the intercepting the crash stack information sent by the first functional module to the installation-free application includes:

A hook function is used to intercept the first function for delivering the crash stack information.
The method according to claim 1, wherein the installation-free application is a game application.
The method according to claim 1, wherein the program code of the installation-free application is implemented by Java language, C language, C++ language, C# language, JavaScript language, ActionScript language, or lua language.
The method according to claim 1, wherein the obtaining the crash stack information sent by the first functional module to the installation-free application includes:

Receive the crash stack information sent by the first function module.
The method according to claim 1, wherein said running the application program of the installation-free framework comprises:

Platform applications running on said operating system.
A crash information collection device, characterized in that the device includes:

An acquisition unit, configured to acquire crash stack information sent to the installation-free application by the first functional module, the crash stack information is used to describe the operation failure of the installation-free application, and the first functional module is a functional module in the operating system of the device carrying the installation-free application;

A sending unit, configured to send the crash stack information to the application running the installation-free framework.
A device, characterized in that the device includes a processor and a memory;

The processor is configured to execute instructions stored in the memory, so that the device executes the method according to any one of claims 1-7.
A computer-readable storage medium, characterized by comprising instructions, the instructions instructing a device to execute the method according to any one of claims 1-7.
A computer program product, characterized in that, when the computer program product is run on a computer, the computer is made to execute the method according to any one of claims 1 to 7.