CN110968471A - Program crash problem reporting method, storage medium, electronic device and system - Google Patents
Program crash problem reporting method, storage medium, electronic device and system Download PDFInfo
- Publication number
- CN110968471A CN110968471A CN201811161369.5A CN201811161369A CN110968471A CN 110968471 A CN110968471 A CN 110968471A CN 201811161369 A CN201811161369 A CN 201811161369A CN 110968471 A CN110968471 A CN 110968471A
- Authority
- CN
- China
- Prior art keywords
- crash
- function
- program
- file
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000003860 storage Methods 0.000 title claims abstract description 18
- 230000006870 function Effects 0.000 claims description 156
- 238000004590 computer program Methods 0.000 claims description 26
- 230000008569 process Effects 0.000 claims description 8
- 238000004891 communication Methods 0.000 claims description 5
- 230000006872 improvement Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 10
- 230000002159 abnormal effect Effects 0.000 description 4
- 230000003068 static effect Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000026676 system process Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- VLCQZHSMCYCDJL-UHFFFAOYSA-N tribenuron methyl Chemical compound COC(=O)C1=CC=CC=C1S(=O)(=O)NC(=O)N(C)C1=NC(C)=NC(OC)=N1 VLCQZHSMCYCDJL-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/323—Visualisation of programs or trace data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a program crash problem reporting method, a storage medium, electronic equipment and a system, which relate to the technical field of computers, and the method comprises the following steps: creating and registering a self-defined crash processing function in the terminal user equipment; when the program crash problem occurs, the terminal user equipment calls a crash processing function to create a crash field file; calling a pointer address of a Dump file write-in function by the terminal user equipment, and writing program crash data into a crash field file by using the Dump file write-in function; and the terminal user equipment reports the crash field file to the server by using the NetworkManager component. The method and the device for analyzing the program crash data can acquire the program crash data and report the program crash data to the server on the premise of not changing the system data of the terminal user equipment, so that a worker can analyze the program crash condition on the premise of not influencing the continuous work of the terminal user equipment, and convenience is provided for the improvement of subsequent programs.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method, a storage medium, electronic equipment and a system for reporting program crash problems.
Background
When a software program runs, a program crash situation may occur, and the computer system can record the program crash situation to obtain program crash data and can analyze the program crash data if necessary;
however, when a worker calls program crash data to analyze the crash reasons of the software program, the worker often obtains the program crash data which is processed by a computer system in advance, so that the worker cannot obtain the initial program crash data when the program crash occurs, and cannot accurately analyze the causes of the software program crash;
therefore, a method for reporting program crash problem is urgently needed, which directly obtains program crash data and provides data basis for improving subsequent programs.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a method for reporting program crash problems, which is used for acquiring program crash data and reporting the program crash data to a server on the premise of not changing the system data of terminal user equipment, so that a worker can analyze the program crash condition on the premise of not influencing the continuous work of the terminal user equipment, and convenience is provided for the improvement of subsequent programs.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows:
in a first aspect, the present invention provides a method for reporting program crash problems, which includes the following steps:
creating and registering a self-defined crash processing function in terminal user equipment, wherein the crash processing function is used for acquiring a crash field file for creating and recording program crash data related to program crash;
when the program crash problem occurs, the terminal user equipment calls a crash processing function to create a crash field file;
calling a pointer address of a Dump file write-in function by the terminal user equipment, and writing program crash data into the crash field file by using the Dump file write-in function;
and the terminal user equipment reports the crash field file to a server by using the NetworkManager component.
On the basis of the above scheme, the terminal user equipment calls a pointer address of a Dump file write-in function, and writes program crash data into the crash field file by using the Dump file write-in function, specifically including the following steps:
acquiring an API (application program interface) of a system and loading a bottom module of the system;
calling a GetProcAddress function to obtain a pointer address of a Dump file write-in function provided by a system bottom layer module;
and calling the Dump file write-in function, and storing program crash data into the crash field file.
On the basis of the scheme, the method further comprises a process of acquiring the crash field file by the network manager component, and the method specifically comprises the following steps:
acquiring a file handle of the crashed field file;
and extracting program crash data stored in the crash field file according to the file handle.
On the basis of the scheme, the method for reporting the crash field file to the server by the terminal user equipment by using the NetworkManager component specifically comprises the following steps:
the terminal user equipment calls a Connect interface, and establishes a communication channel between the NetworkManager component and the server background;
and calling a send interface to transmit and report the crash site file to a server background through Http.
On the basis of the above scheme, when creating and registering a customized crash processing function in the end user device, the method further includes the following steps:
and defining the pointer address of the crash processing function for callback use when the program crash problem occurs.
On the basis of the above scheme, when creating and registering a customized crash processing function in the end user device, the method further includes the following steps:
and calling a SetUnhandleExceptionFilter function, and registering the pointer address of the crash processing function to the system.
In a second aspect, the present invention further provides a storage medium, where a computer program is stored on the storage medium, and when the computer program is executed by a processor, the method for reporting a program crash problem in the first aspect is implemented.
In a third aspect, the present invention further provides an electronic device, including a memory and a processor, where the memory stores a computer program running on the processor, and the processor executes the computer program to implement the method for reporting a program crash problem in the first aspect.
In a fourth aspect, the present invention further provides a system for reporting program crash problems, which includes:
the system comprises a crash processing function creating unit, a crash processing unit and a crash processing unit, wherein the crash processing function creating unit is used for creating and registering a self-defined crash processing function in terminal user equipment, and the crash processing function is used for acquiring a crash field file for creating and recording program crash data related to program crash;
the crash field file creating unit is used for calling a crash processing function by the terminal user equipment and creating a crash field file when the program crash problem occurs;
the crash data writing unit is used for calling a pointer address of a Dump file writing function and writing program crash data into the crash field file by using the Dump file writing function;
and the crash problem reporting unit is used for reporting the crash field file to a server by utilizing the network manager component.
On the basis of the above technical solution, the crash data writing unit includes:
the loading subunit is used for acquiring an API (application program interface) of the system and loading a system bottom layer module;
the address acquisition subunit is used for calling a GetProcAddress function and acquiring a pointer address of a Dump file write-in function provided by a system bottom layer;
and the data writing subunit is used for calling the Dump file writing function and storing program crash data into the crash field file.
Compared with the prior art, the invention has the advantages that:
on the premise of ensuring the normal operation of the system and not changing the data of the system, the invention obtains the program crash data and reports the program crash data to the server by means of the Dump file write-in function and the NetworkManager component, so that the worker can analyze the program crash condition on the premise of not influencing the continuous work of the terminal user equipment, and the invention provides convenience for the improvement of the subsequent program.
Drawings
Fig. 1 is a flowchart illustrating a procedure of a method for reporting a program crash problem according to an embodiment of the present invention;
fig. 2 is a flowchart of step 3 of a method for reporting a program crash problem according to an embodiment of the present invention;
fig. 3 is a block diagram of a system for reporting program crash problems according to a fourth embodiment of the present invention;
fig. 4 is a block diagram illustrating a structure of a crash data writing unit in the system for reporting program crash problems according to the fourth embodiment of the present invention;
in the figure: 1. a crash processing function creation unit; 2. a crash field file creation unit; 3. a crash data write unit; 30. a load subunit; 31. an address acquisition subunit; 32. a data write subunit; 4. and a crash problem reporting unit.
Detailed Description
Interpretation of terms:
the Dump file is a memory mirror image of a process, the execution state of a program can be saved in the Dump file through a debugger, and the Dump file is used for a driver writer to debug the driver;
NetworkManager component, NetworkManager, is a background service that is networked by a management system and reports its status via the D-BUS, NetworkManager is a client program that allows a user to manage network connections
static LONG WINAPI HandleException (EXCEPTION _ POINTERS. EXinfo) for creating custom crash handling functions;
a SetUnhandleExceptionFilter function for completing registration of a callback function address of a custom crash processing function;
a generatefulldumfile function, which is used for the creation of a crash field function;
GetProcAddress function, GetProcAddress is a computer function that is functional to retrieve an output library function address in a specified Dynamic Link Library (DLL);
the function of the LoadLibrary () function is to load a specified dynamic link library and map the specified dynamic link library to the address space used by the current process, and in the invention, the LoadLibrary ("dbghelp.dll") is loaded into "dbghelp.dll";
minidumpwriteudpump, which is an API in MS dbghlp.dll, for deriving the Dump of a currently running program;
the CreateFile function is a multi-functional function that opens or creates a file or I/O device and returns an accessible handle: consoles, communication resources, directories (read-only open), disk drives, files, mailslots, pipes;
the ReadFile function, it is used for reading out the data into a file from the position pointed to by pointer of the file, and support synchronous and asynchronous operation.
Embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.
The embodiment of the invention provides a program crash problem reporting method, a storage medium, electronic equipment and a system, which are used for acquiring program crash data and reporting the program crash data to a server by means of a Dump file write-in function and a network manager component on the premise of ensuring the normal operation of the system and not changing the data of the system, so that a worker can analyze the program crash condition on the premise of not influencing the continuous work of terminal user equipment, and convenience is provided for the improvement of subsequent programs.
In order to achieve the technical effects, the general idea of the application is as follows:
a method for reporting program crash problem includes the following steps:
s1, creating and registering a self-defined crash processing function in the terminal user equipment, wherein the crash processing function is used for acquiring a crash field file for creating and recording program crash data related to program crash;
s2, when the program crash problem occurs, the terminal user equipment calls a crash processing function to create a crash field file;
s3, the terminal user equipment calls the pointer address of the Dump file writing function, and the Dump file writing function is used for writing the program crash data into the crash field file;
and S4, the terminal user equipment reports the crash field file to the server by using the NetworkManager component.
Example one
Referring to fig. 1 and 2, an embodiment of the present invention provides a method for reporting a program crash problem, including the following steps:
s1, creating and registering a self-defined crash processing function in the terminal user equipment, wherein the crash processing function is used for acquiring a crash field file for creating and recording program crash data related to program crash;
s2, when the program crash problem occurs, the terminal user equipment calls a crash processing function to create a crash field file;
s3, the terminal user equipment calls the pointer address of the Dump file writing function, and the Dump file writing function is used for writing the program crash data into the crash field file;
and S4, the terminal user equipment reports the crash field file to the server by using the NetworkManager component.
In the embodiment of the invention, the user-defined crash processing function is used for creating the crash field file, the own Dump file writing function of the system is called, the program crash data is written into the crash field file, and finally the network manager component of the system is used for reporting the crash field file to the server.
It should be noted that the method is mainly based on windows system.
In step S1, the embodiment of the present invention creates a self-defined crash handling function in the end user device in advance, and registers the function in the system, during actual operation, an address of a handling function pointer of abnormal crash may be defined first, so as to receive a callback usage when the system monitors program abnormal crash, and specifically, the operation may be completed by using static LONG window runtime EXCEPTION (EXCEPTION _ POINTERS EXCEPTION) code,
the code "static LONG WINAPI handle EXCEPTION" (EXCEPTION _ tasks) indicates: debugging data when a program crashes and data automatically filled by windows, including data such as call stacks, thread environments and the like, are stored in the exinfo data structure; then, a local file is created in a program directory, a suffix name is set to dmp, and then data in the exinfo is written into the created local file;
registering a self-defined crash processing function, namely registering a callback function address of the self-defined crash processing function to the system, so that the problem that the system processes crash by itself to cause that the method cannot obtain initial program crash data is avoided, and specifically, a SetUnhandleExceptionFilter function can be called to complete the registration of the callback function address;
therefore, it should be noted that, when creating and registering a customized crash handling function in the end user device, the method further includes the following steps:
and defining the pointer address of the crash processing function for callback use when the program crash problem occurs.
In addition, when the user-defined crash processing function is created and registered in the terminal user equipment, the method further comprises the following steps:
and calling a SetUnhandleExceptionFilter function, and registering the pointer address of the crash handling function in the system.
In step S2, when the program crash problem occurs, since the registration is completed, the system of the end-user device may call the crash processing function to create the crash site file, and during the specific operation, the creation of the crash site file may be performed by using the generatefulldumfile function.
And after the crash site file is created, step S3 is started, where the end user device calls the pointer address of the Dump file write function, and writes the program crash data into the crash site file by using the Dump file write function, where the step specifically includes the following steps:
a1, acquiring an API (application program interface) of the system, and loading a system bottom module;
a2, calling a GetProcAddress function, and acquiring a pointer address of a Dump file write-in function provided by a system bottom layer module;
a3, calling a Dump file write-in function, and storing program crash data into a crash field file;
in the step, the program crash data is stored in a crash field file by using the function and the function of the system, and a specific implementation mode is provided for the actual operation condition:
calling a LoadLibrary (dbghelp.dll) function to load a system bottom module, wherein before the system is started, because a windows system does not have an open related API (application programming interface), the API in a windows.dll file needs to be manually obtained by loading a DLL (delay locked loop);
secondly, calling a GetProcAddress (module, "MiniDumpWriteDump") function to acquire a pointer address of a Dump file writing function provided by the bottom layer of the windows system;
and thirdly, according to the MiniDumpWriteDump function pointer obtained in the second step, namely the pointer address of the Dump file writing function provided by the bottom layer of the windows system, writing program crash data into a previously completed common crash field file by using the Dump file writing function.
Before step S4 begins, the embodiment of the present invention further includes a process in which the NetworkManager component acquires a crash site file, and specifically includes the following steps:
acquiring a file handle of a crashed field file;
extracting program crash data stored in the crash field file according to the file handle;
during specific operation, a CreateFile function can be called to open a file handle of the crash field file, wherein the file handle is mainly used as a query basis and provides a data searching direction for reading the contents of the crash file into a memory subsequently;
and then calling a ReadFile function according to the obtained file handle, extracting program crash data stored in the crash field file, and reading the data of the crash field file into an internal memory.
After the above steps are completed, step S4 is performed, and the terminal user device in step S4 reports the crash site file to the server by using the NetworkManager component, which specifically includes the following steps:
the terminal user equipment calls a Connect interface, and a communication channel is established between the NetworkManager component and the server background;
and calling the send interface to transmit and report the crash field file to the server background through Http.
Based on the same inventive concept, the present application provides an embodiment of a system for reporting program crash problems corresponding to the embodiment, which is detailed in embodiment two
Example two
As shown in fig. 3 and 4, a second embodiment of the present invention provides a system for reporting a program crash problem, where the system is suitable for an end user device, and based on an own operating system of the end user device, the system includes:
a crash processing function creating unit 1, configured to create and register a self-defined crash processing function in a terminal user device, where the crash processing function is used to acquire a crash field file for creating and recording program crash data related to program crash;
a crash field file creation unit 2, configured to, when a program crash problem occurs, call a crash processing function by the end user device, and create a crash field file;
the crash data writing unit 3 is used for calling a pointer address of a Dump file writing function and writing program crash data into a crash field file by using the Dump file writing function;
and the crash problem reporting unit 4 is used for reporting the crash field file to the server by using the NetworkManager component.
In the embodiment of the invention, the user-defined crash processing function is used for creating the crash field file, the Dump file writing function is called, the program crash data is written into the crash field file, and the network manager component is used for reporting the crash field file to the server.
It should be noted that the method is mainly based on windows system.
In the embodiment of the invention, when the crash processing function creating unit 1 works, a self-defined crash processing function is created in the terminal user equipment in advance, and the function is registered in the operating system, when in actual operation, the address of a processing function pointer of abnormal crash can be defined first, and the address is used for receiving a callback when the operating system monitors program abnormal crash, and the operation can be completed by using a static LONG WINAPI handle EXCEPTION (EXCEPTION _ POINTER. info) code,
registering a self-defined crash processing function, namely registering a callback function address of the self-defined crash processing function to the operating system, so that the condition that the operating system processes the crash by itself to cause that the system cannot obtain initial program crash data is avoided, and specifically, a SetUnhand ledExceptionFilter function can be called to complete the registration of the callback function address;
therefore, it should be noted that, when creating and registering a customized crash handling function in the end user device, the method further includes the following steps:
and defining the pointer address of the crash processing function for callback use when the program crash problem occurs.
In addition, when the user-defined crash processing function is created and registered in the terminal user equipment, the method further comprises the following steps:
and calling a SetUnhandleExceptionFilter function, and registering the pointer address of the crash handling function in the system.
When the program crash problem occurs, because the registration is completed, the operating system of the end user device calls the crash processing function by using the crash field File creating unit 2 to create the crash field File, and during the specific operation, the creation of the crash field File can be performed by using the generatefullldump File function.
After the crash field file is created, the crash data writing unit 3 starts to work, the terminal user equipment calls the pointer address of the Dump file writing function, and the Dump file writing function is used for writing the program crash data into the crash field file;
therefore, in the embodiment of the present invention, the crash data writing unit 3 includes:
a loading subunit 30, configured to obtain an API interface of the system and load a system bottom module;
an address obtaining subunit 31, configured to call a GetProcAddress function, and obtain a pointer address of a Dump file write function provided by a system bottom layer;
the data writing subunit 32 is used for calling a Dump file writing function and storing program crash data into a crash field file;
in the process, program crash data is stored in a crash field file by utilizing the functions and functions of an operating system, and a specific implementation mode is provided for the actual operation condition:
calling a LoadLibrary (dbghelp.dll) function to load a system bottom module, wherein before the system is started, because a windows system does not have an open related API (application programming interface), the API in a windows.dll file needs to be manually obtained by loading a DLL (delay locked loop);
secondly, calling a GetProcAddress (module, "MiniDumpWriteDump") function to acquire a pointer address of a Dump file writing function provided by the bottom layer of the windows system;
and thirdly, according to the MiniDumpWriteDump function pointer obtained in the second step, namely the pointer address of the Dump file writing function provided by the bottom layer of the windows system, writing program crash data into a previously completed common crash field file by using the Dump file writing function.
Before the crash problem reporting unit 4 reports, the crash problem reporting unit 4 of the embodiment of the present invention further includes a work process of the NetworkManager component acquiring the crash field file, and specifically includes the following steps:
acquiring a file handle of a crashed field file;
extracting program crash data stored in the crash field file according to the file handle;
during specific operation, a CreateFile function can be called to open a file handle of the crash field file, wherein the file handle is mainly used as a query basis and provides a data searching direction for reading the contents of the crash file into a memory subsequently;
and then calling a ReadFile function according to the obtained file handle, extracting program crash data stored in the crash field file, and reading the data of the crash field file into an internal memory.
After the above steps are completed, the crash problem reporting unit 4 reports the crash field file to the server by using the NetworkManager component, and when the crash problem reporting unit 4 works, the terminal user equipment specifically includes the following steps:
the terminal user equipment calls a Connect interface, and a communication channel is established between the NetworkManager component and the server background;
and calling the send interface to transmit and report the crash field file to the server background through Http.
Based on the same inventive concept, the present application provides an embodiment of a storage medium corresponding to the embodiment described in the third embodiment
EXAMPLE III
A third embodiment of the invention provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out all or part of the method steps of the first embodiment.
The present invention can implement all or part of the flow in the first embodiment, and can also be implemented by using a computer program to instruct related hardware, where the computer program can be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned method embodiments can be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, recording medium, U.S. disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), random-Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution media, and the like. It should be noted that the computer readable medium may contain other components which may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, in accordance with legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunications signals.
Based on the same inventive concept, the present application provides an embodiment of an electronic device corresponding to the first embodiment, which is detailed in the fourth embodiment
Example four
The fourth embodiment of the present invention further provides an electronic device, which includes a memory and a processor, wherein the memory stores a computer program running on the processor, and the processor executes the computer program to implement all or part of the method steps in the first embodiment.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, the processor being the control center of the computer device and the various interfaces and lines connecting the various parts of the overall computer device.
The memory may be used to store computer programs and/or modules, and the processor may implement various functions of the computer device by executing or executing the computer programs and/or modules stored in the memory, as well as by invoking data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, video data, etc.) created according to the use of the cellular phone, etc. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart media a Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, server, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), servers and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A method for reporting program crash problem is characterized by comprising the following steps:
creating and registering a self-defined crash processing function in terminal user equipment, wherein the crash processing function is used for acquiring a crash field file for creating and recording program crash data related to program crash;
when the program crash problem occurs, the terminal user equipment calls a crash processing function to create a crash field file;
calling a pointer address of a Dump file write-in function by the terminal user equipment, and writing program crash data into the crash field file by using the Dump file write-in function;
and the terminal user equipment reports the crash field file to a server by using the NetworkManager component.
2. The method of claim 1, wherein the end user device invokes a pointer address of a Dump file write function, and writes program crash data into the crash field file using the Dump file write function, comprising the steps of:
acquiring an API (application program interface) of a system and loading a bottom module of the system;
calling a GetProcAddress function to obtain a pointer address of a Dump file write-in function provided by a system bottom layer module;
and calling the Dump file write-in function, and storing program crash data into the crash field file.
3. The method of claim 1, further comprising a process of the NetworkManager component obtaining the crash site file, specifically comprising the steps of:
acquiring a file handle of the crashed field file;
and extracting program crash data stored in the crash field file according to the file handle.
4. The method of claim 1, wherein the end-user device reports the crash site file to a server using the NetworkManager component, and specifically comprises the following steps:
the terminal user equipment calls a Connect interface, and establishes a communication channel between the NetworkManager component and the server background;
and calling a send interface to transmit and report the crash site file to a server background through Http.
5. The method of claim 1, wherein creating and registering a custom crash handling function in an end-user device further comprises:
and defining the pointer address of the crash processing function for callback use when the program crash problem occurs.
6. The method of claim 5, wherein creating and registering a custom crash handling function in an end-user device further comprises:
and calling a SetUnhandleExceptionFilter function, and registering the pointer address of the crash processing function to the system.
7. A storage medium having a computer program stored thereon, characterized in that: the computer program, when executed by a processor, implements the method of any of claims 1 to 6.
8. An electronic device comprising a memory and a processor, the memory having stored thereon a computer program that runs on the processor, characterized in that: the processor, when executing the computer program, implements the method of any of claims 1 to 6.
9. A system for reporting program crash problems, comprising:
the system comprises a crash processing function creating unit, a crash processing unit and a crash processing unit, wherein the crash processing function creating unit is used for creating and registering a self-defined crash processing function in terminal user equipment, and the crash processing function is used for acquiring a crash field file for creating and recording program crash data related to program crash;
the crash field file creating unit is used for calling a crash processing function by the terminal user equipment and creating a crash field file when the program crash problem occurs;
the crash data writing unit is used for calling a pointer address of a Dump file writing function and writing program crash data into the crash field file by using the Dump file writing function;
and the crash problem reporting unit is used for reporting the crash field file to a server by utilizing the network manager component.
10. The system of claim 9, wherein the crash data write unit comprises:
the loading subunit is used for acquiring an API (application program interface) of the system and loading a system bottom layer module;
the address acquisition subunit is used for calling a GetProcAddress function and acquiring a pointer address of a Dump file write-in function provided by a system bottom layer;
and the data writing subunit is used for calling the Dump file writing function and storing program crash data into the crash field file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811161369.5A CN110968471A (en) | 2018-09-30 | 2018-09-30 | Program crash problem reporting method, storage medium, electronic device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811161369.5A CN110968471A (en) | 2018-09-30 | 2018-09-30 | Program crash problem reporting method, storage medium, electronic device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110968471A true CN110968471A (en) | 2020-04-07 |
Family
ID=70029412
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811161369.5A Pending CN110968471A (en) | 2018-09-30 | 2018-09-30 | Program crash problem reporting method, storage medium, electronic device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110968471A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434362A (en) * | 2021-06-24 | 2021-09-24 | 广州欢网科技有限责任公司 | Method and device for automatically early warning when Android program is abnormal |
| CN113918377A (en) * | 2021-12-16 | 2022-01-11 | 深圳软牛科技有限公司 | Method, device and equipment for positioning C + + program crash and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106484617A (en) * | 2016-10-09 | 2017-03-08 | 武汉斗鱼网络科技有限公司 | Statistical method and system are automatically analyzed for the dump file of Windows software product |
| CN108170552A (en) * | 2018-01-05 | 2018-06-15 | 武汉斗鱼网络科技有限公司 | A kind of method, apparatus and equipment for capturing Dump files |
-
2018
- 2018-09-30 CN CN201811161369.5A patent/CN110968471A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106484617A (en) * | 2016-10-09 | 2017-03-08 | 武汉斗鱼网络科技有限公司 | Statistical method and system are automatically analyzed for the dump file of Windows software product |
| CN108170552A (en) * | 2018-01-05 | 2018-06-15 | 武汉斗鱼网络科技有限公司 | A kind of method, apparatus and equipment for capturing Dump files |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434362A (en) * | 2021-06-24 | 2021-09-24 | 广州欢网科技有限责任公司 | Method and device for automatically early warning when Android program is abnormal |
| CN113918377A (en) * | 2021-12-16 | 2022-01-11 | 深圳软牛科技有限公司 | Method, device and equipment for positioning C + + program crash and storage medium |
| CN113918377B (en) * | 2021-12-16 | 2022-03-25 | 深圳软牛科技有限公司 | Method, device and equipment for positioning C + + program crash and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107832100B (en) | APK plug-in loading method and terminal thereof | |
| CN108170552B (en) | Method, device and equipment for capturing Dump file | |
| CN107644075B (en) | Method and device for collecting page information | |
| CN111090536A (en) | Method, device, medium and electronic equipment for acquiring memory leakage information | |
| CN111290949A (en) | Process daemon method and equipment | |
| CN110727581A (en) | Collapse positioning method and electronic equipment | |
| CN114237498A (en) | Snapshot generation method and system for cloud native storage data volume | |
| CN110968471A (en) | Program crash problem reporting method, storage medium, electronic device and system | |
| CN113282436A (en) | Event processing method, device, equipment and storage medium | |
| CN115390991A (en) | Virtual machine import and export method, device, equipment and storage medium | |
| CN111782520A (en) | Test method and device and electronic equipment | |
| CN111294377B (en) | Dependency network request sending method, terminal device and storage medium | |
| CN109725887B (en) | Data interaction method and device based on message research and development framework and terminal equipment | |
| CN110881224B (en) | Network long connection method, device, equipment and storage medium | |
| CN111158987A (en) | Health check method and device of micro-service architecture | |
| CN111045698A (en) | Redundant picture deleting method and device, electronic equipment and storage medium | |
| CN111949297B (en) | Block chain intelligent contract upgrading method and device and electronic equipment | |
| CN114328097A (en) | File monitoring method and device, electronic equipment and storage medium | |
| CN111400091B (en) | Factory setting restoration method, factory setting restoration device and mobile terminal | |
| CN112650689A (en) | Test method, test device, electronic equipment and storage medium | |
| CN108616603B (en) | Method and system for synchronizing internal and external network data | |
| CN116956272A (en) | Authority calling monitoring method and device and electronic equipment | |
| CN114157662A (en) | Cloud platform parameter adaptation method and device, terminal equipment and storage medium | |
| CN115437551A (en) | Data cloning method, device, storage medium and computer program product | |
| CN111143583A (en) | Method and device for monitoring data change of media database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200407 |