CN114756393A - Program crash detection method, device, server and storage medium - Google Patents

Program crash detection method, device, server and storage medium Download PDF

Info

Publication number
CN114756393A
CN114756393A CN202210208459.5A CN202210208459A CN114756393A CN 114756393 A CN114756393 A CN 114756393A CN 202210208459 A CN202210208459 A CN 202210208459A CN 114756393 A CN114756393 A CN 114756393A
Authority
CN
China
Prior art keywords
program
data
interface
crash
program crash
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
Application number
CN202210208459.5A
Other languages
Chinese (zh)
Inventor
杨金华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Securities Co Ltd
Original Assignee
Ping An Securities Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ping An Securities Co Ltd filed Critical Ping An Securities Co Ltd
Priority to CN202210208459.5A priority Critical patent/CN114756393A/en
Publication of CN114756393A publication Critical patent/CN114756393A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079Root cause analysis, i.e. error or fault diagnosis
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793Remedial or corrective actions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3055Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application is suitable for the technical field of pedestal operation and maintenance, and provides a program crash detection method, a device, a server and a storage medium, wherein the program crash detection method comprises the following steps: monitoring whether a preset program is crashed or not through a monitoring interface of a secondary packaged memory leakage detection frame; when the program is crashed in the preset program, program crash data are generated; and performing data analysis and data persistence on the program crash data through an external log interface of the secondarily-packaged memory leak detection framework. According to the method, the use condition of the application program is automatically monitored by utilizing a secondary packaged memory leak detection framework and adopting a mode of implanting a monitoring interface into a monitoring node in a source code of the application program, so that detailed data and operation steps when the program collapse problem occurs in the use process of the application program can be timely and accurately obtained automatically, the application program is not required to be unloaded, and manual operation is not required.

Description

Program crash detection method, device, server and storage medium
Technical Field
The present application relates to the field of pedestal operation and maintenance technologies, and in particular, to a method and an apparatus for detecting program crash, a server, and a storage medium.
Background
Program Crash (APP Crash) is a specific fault in Windows Vista and Windows 7, and problems causing program Crash are many, for example, a Dynamic-Link Libraries (DLL) file loading error, software incompatibility, and adding or losing files may cause program Crash. Different errors also need to be solved in different ways, and program crashes are mostly caused by plug-ins. The existing solution is to check the plug-in and uninstall the recently installed Application (APP), requiring manual operation by the user.
Disclosure of Invention
In view of this, embodiments of the present application provide a method, an apparatus, a server, and a storage medium for detecting program crash, so as to solve the problem that the existing method for solving program crash is to check a plug-in, uninstall a recently installed application, and require a user to perform a manual operation.
A first aspect of an embodiment of the present application provides a method for detecting program crash, including:
monitoring whether the program crash occurs to the preset program or not through a monitoring interface of a secondary packaged memory leakage detection framework;
when the preset program is crashed, generating program crash data;
and performing data analysis and data persistence on the program crash data through an external log interface of the secondary packaged memory leak detection framework.
A second aspect of an embodiment of the present application provides a program crash detection apparatus, including:
the monitoring unit is used for monitoring whether the program crash occurs to the preset program through a monitoring interface of the secondary packaged memory leakage detection framework;
the generating unit is used for generating program crash data when the preset program is subjected to program crash;
and the analysis unit is used for carrying out data analysis and data persistence on the program crash data through an external log interface of the secondary packaged memory leak detection framework.
A third aspect of the embodiments of the present application provides a server, including a memory, a processor, and a computer program stored in the memory and operable on the server, where the processor implements the steps of the program crash detection method provided in the first aspect when executing the computer program.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the program crash detection method provided in the first aspect.
In the method for detecting program crash provided in the first aspect of the embodiment of the present application, whether a preset program crashes or not is monitored through a monitoring interface of a memory leak detection framework packaged for the second time; when the program of the preset program is crashed, generating program crash data; the method comprises the steps of analyzing data and persisting data of program collapse data through an external log interface of a secondary-packaged memory leak detection framework, automatically monitoring the use condition of an application program by utilizing the secondary-packaged memory leak detection framework and adopting a mode of implanting a monitoring interface into a monitoring node in a source code of the application program, automatically acquiring detailed data and operation steps when the program collapse problem occurs in the use process of the application program in time and accurately, and not needing to unload the application program and manually operate.
It is understood that the beneficial effects of the second to fourth aspects can be seen from the description of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a first flowchart illustrating a program crash detection method according to an embodiment of the present application;
FIG. 2 is a second flowchart illustrating a program crash detection method according to an embodiment of the present disclosure;
FIG. 3 is a third flowchart illustrating a program crash detection method according to an embodiment of the present disclosure;
FIG. 4 is a fourth flowchart illustrating a program crash detection method according to an embodiment of the present disclosure;
FIG. 5 is a schematic structural diagram of a program crash detection apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather mean "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
The embodiment of the application provides a program crash detection method, which can be executed by a processor of a server when a corresponding computer program is run, and can automatically monitor the use condition of the application program by using a secondary-packaged memory leak detection framework (leak cancer) and adopting a mode of implanting a monitoring interface into a monitoring node in a source code of the application program, so that detailed data and operation steps when a program crash problem occurs in the use process of the application program can be timely, accurately and automatically obtained.
In an application, the application program may be any computer program that needs program crash detection and can run on a server and a client, for example, a security program or a futures program.
In application, the server may be any computing device having functions of running and processing computer programs, such as a server, a tablet computer, a notebook computer, a Personal computer, a netbook, a Personal Digital Assistant (PDA), a desktop computer, and the like. The client may be a cell phone, a tablet, a wearable device, an Augmented Reality (AR) device, a Virtual Reality (VR) device, a laptop, a personal computer, a netbook, a personal digital assistant, a desktop computer, and so on.
As shown in fig. 1, the method for detecting program crash provided in the embodiment of the present application includes the following steps S101 to S104:
and S101, carrying out secondary packaging on the memory leakage detection frame.
In application, before the server monitors the preset program by running the memory leak detection framework of the secondary packaging, the memory leak detection framework needs to be implanted into a source code of the preset program, so as to realize the secondary packaging of the memory leak detection framework. The preset program is any application program that a user of the server or the client wants to monitor.
In application, a user of the server can control the server through the man-machine interaction device, and pull the source code of the locally stored preset program from the current server, or pull the source code of the preset program from other servers, and then implant the memory leak detection framework into the source code of the preset program, so as to implement secondary packaging of the memory leak detection framework.
In application, the human-computer interaction device may include, but is not limited to, at least one of a keyboard, a physical key, a touch sensor, a gesture recognition sensor, and a voice recognition unit, so that a user may operate the server in a corresponding touch manner, gesture operation manner, or voice control manner. The touch control mode of the entity key can be pressing or shifting, the touch control mode of the touch control sensor can be pressing or touching, and the like, and the gesture for controlling the server can be set by a user according to actual needs in a user-defined mode or default setting in factory leaving. The voice recognition unit can comprise a microphone and a voice recognition chip, and the voice used for controlling the server can be set by a user in a user-defined mode through a man-machine interaction device of the server in advance or set by default when the user leaves a factory. The human-computer interaction device may be integrated in the server, for example, the touch sensor may be integrated with a display of the server to form a touch display. The man-machine interaction device can also be used as an external device of the server and is in communication connection with the server, for example, a keyboard and a microphone can be in communication connection with the server through a USB interface of the server.
As shown in fig. 2, in an embodiment, the step S101 specifically includes the following steps S201 to S204:
step S201, implanting a physical address for data persistence in a memory leak detection framework.
In an application, the data persistence may be performed by storing the data in a database, and correspondingly, the physical address may be a storage address of the data, and the storage address may exist in the form of an address link. The database may be a relational database management system (mySQL) database.
Step S202, an external log interface of the memory leak detection framework is opened.
In the application, the log is a log generated when the preset program crashes, and is used for recording program crash related data generated when the preset program crashes. The external log interface is an interface for opening to the outside so that other programs or tools can acquire and analyze program crash related data, for example, a query interface for querying program crash related data, a filter interface for filtering program crash related data, a download interface for downloading program crash related data, and the like.
In one embodiment, the outbound log interface may include, but is not limited to, at least one of a query interface, a filter interface, and a download interface.
Step S203, pulling the source code of the preset program, and implanting a monitoring interface in a preset monitoring node in the source code of the preset program.
In application, a user can control any node position to be monitored in a source code of a pulled preset program of a server, and a monitoring interface is implanted for monitoring the node position in the process that a client runs and uses the preset program. The node location where the monitoring interface is embedded is related to the type of the preset program, for example, when the preset program is a securities program or a futures program, the monitoring interface includes, but is not limited to, an ordering interface for monitoring ordering operations of securities or futures, a market query interface for monitoring market query operations of securities or futures, a user login interface for monitoring user login operations of securities programs or futures programs, and a user registration interface for monitoring user registration operations of securities programs or futures programs.
In one embodiment, the monitoring interface includes, but is not limited to, at least one of an order placement interface, a market query interface, a user login interface, and a user registration interface.
Step S204, the configuration packet of the memory leak detection framework is configured to the configuration packet of the source code of the preset program, and the secondary packaging of the memory leak detection framework is completed.
In the application, after the operations in steps S201 to S203 are completed, the configuration package (e.g., Jar package) of the memory leak detection framework is configured into the configuration package (e.g., packaging configuration file) of the source code of the preset program, and secondary packaging of the memory leak detection framework is completed.
In one embodiment, step S204 is followed by:
generating a logic address of a secondary packaged memory leakage detection frame;
and configuring the logic address on a preset webpage interface, wherein the preset webpage interface is used for carrying out visual management on the memory leak detection framework.
In the application, before step S101, a step of generating a preset web page (web) interface may be further included, where the preset web page interface is displayed on the server, and a user may control the server through the human-computer interaction device to operate the preset web page interface, so as to implement visual management on the memory leak detection framework before and after the secondary packaging. The logical address may specifically be an Internet Protocol (IP) address. The logic address is configured on the preset webpage interface, so that a user can access the logic address by operating the preset webpage interface, and visual management of the memory leak detection framework before and after secondary packaging is realized. The logical address can be displayed on a main interface or any secondary interface of the preset webpage interface, such as a secondary interface or a tertiary interface.
And S102, monitoring whether the program crash occurs to the preset program through a monitoring interface of the secondary packaged memory leakage detection framework.
In application, after the memory leak detection framework is implanted into the source code of the preset program in advance to realize secondary packaging of the memory leak detection framework, the memory leak detection framework of the secondary packaging can be operated to monitor whether the program crash occurs in the use process of the preset program.
Step S103, when the program is crashed in the preset program, program crash data is generated;
and step S104, performing data analysis and data persistence on the program crash data through an external log interface of the secondary packaged memory leak detection framework.
In the application, when the preset program is monitored to have a program crash, a log file for recording data related to the program crash is generated, and the log file may exist in the form of an eXtensible Markup Language (XML) file. The user can control other programs or tools to acquire program crash related data through the external log interface, and analyze and persist the program crash related data.
As shown in fig. 3, in an embodiment, in step S104, performing data parsing and data persistence on program crash data may specifically include steps S301 and S302:
step S301, classifying program crash data;
and step S302, storing the classified program crash data into a database.
In the application, a user may manipulate a preset web interface, and a category for classifying the program crash data is set in advance, specifically, a corresponding log interface may be opened according to different business requirements to classify the program crash data, for example, when the preset program is a securities program or a futures program, the classified program crash data may include order placing data related to order placing operation, market information query data related to market information query operation of securities or futures, user login data related to user login operation of the securities program or the futures program, and user registration data related to user registration operation of registering the securities program or the futures program. Different classes of program crash data may be stored to different databases or different storage spaces of the same database.
As shown in fig. 4, in one embodiment, step S301 may be followed by:
step S401, carrying out multi-dimensional data statistics on the program crash data of each category;
step S402, carrying out multi-dimensional visualization processing on the program crash data of each category according to the dimension of the program crash data of each category.
In application, multiple dimensions may include, but are not limited to: monitoring time, monitoring times, crash time, crash times, and the like. The visualization processing may specifically be to perform multi-dimensional graphical display on the program crash data of each category according to the dimension of the program crash data of each category, for example, the multi-dimensional graphical display is performed in the form of an array diagram, a table, a pie chart, a bar chart, and the like, so that a user can visually check the program crash data of each category, and thus, the analysis on the reason of the preset program crash is facilitated.
In an embodiment, step S401 may specifically include:
recording the program crash data of each category according to the time and the times for monitoring the preset program;
and/or recording the program crash data of each category according to the time and the times of program crash of the preset program.
In application, a user can actively control a preset webpage interface to control the operation of a secondary packaged memory leakage detection framework at any time when needed so as to monitor whether a preset program is crashed or not; the user can also control the preset web interface, and preset the operating frequency (for example, once per minute) of the secondary-packaged memory leak detection framework, so that the secondary-packaged memory leak detection framework can automatically operate according to the preset operating frequency to automatically monitor the preset program.
In application, when the memory leak detection framework runs, program crash data of each category can be recorded according to the time and the times for monitoring a preset program; and recording the program crash data of each category according to the time and the number of times of program crash occurrence of the preset program. The time may be a point in time or a period of time, and may specifically be represented as a date, which may specifically be accurate for the time of year, month, day, hour, minute and second. Each time corresponds to one program crash data, and the association relationship between each time and the corresponding program crash data can be established and persisted.
In application, the association relationship may be a mapping relationship, and may exist in the form of an association relationship Table, and the association relationship Table may be a Look-Up Table (LUT), and may also exist in the form of a Look-Up result which can be searched and output by using other input data. By establishing the association relationship in advance, the calculation resources and the execution time of the server can be effectively saved.
In one embodiment, after step S102, the method includes:
uploading program crash data to a blockchain;
in one embodiment, after step S104, the method includes:
and uploading the program crash data subjected to data analysis to the block chain.
In the application, before and after data analysis is carried out on program crash data, the program crash related data can be uploaded to a block chain (Blockchain), so that the safety and the fair transparency to users can be ensured. The server or the client may download the program crash related data from the blockchain to verify whether the program crash related data is tampered. The blockchain referred to in this example is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, and the like. The block chain, which is essentially a decentralized database, is a string of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, which is used for verifying the validity (anti-counterfeiting) of the information and generating a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
In application, a Memory leak detection framework is a tool for automatically detecting Memory leak for Android developers, the Memory leak detection framework is essentially an open source tool for automatically detecting the Memory leak of the Android application program based on a Memory Analysis Tool (MAT), Java Archive (JAR) provided by the Memory leak detection framework can be packaged into own engineering, once the Memory leak is detected, the Memory leak detection framework can store and Dump (Memory Dump) information, analyze and display the information of the Memory leak through another process, find and locate the Memory leak problem at any time, and do not need to extract a special person to detect the Memory leak problem in a development process every time, thereby greatly facilitating the development of the Android application program.
According to the program crash detection method provided by the embodiment of the application, the data analysis is performed on the program crash data, so that a user of the server can perform effective data capture and data summarization on the program crash data of the client according to relevant strategy rules under the condition that the application program is not subjected to secondary development and demand positioning, the working efficiency and the usability are improved, the program crash problem occurring at the client can be positioned and counted, and the server can perform monitoring on the application program running at the client by one key.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
As shown in fig. 5, an embodiment of the present application further provides a program crash detection apparatus 100, configured to execute the steps in the program crash detection method in the foregoing embodiment, where the program crash detection apparatus 100 includes:
the packaging unit 101 is used for carrying out secondary packaging on the memory leakage detection frame;
the monitoring unit 102 is configured to monitor whether a preset program is crashed through a monitoring interface of the secondary-packaged memory leak detection framework;
the generating unit 103 is configured to generate program crash data when a preset program crashes;
and the analysis unit 104 is configured to perform data analysis and data persistence on the program crash data through an external log interface of the secondary-packaged memory leak detection framework.
In an embodiment, the generating unit is further configured to generate a preset web interface.
In one embodiment, the program crash detection apparatus further comprises:
the data statistics unit is used for carrying out multi-dimensional data statistics on the program crash data of each category;
and the view unit is used for carrying out multi-dimensional view processing on the program crash data of each category according to the dimension of the program crash data of each category.
In one embodiment, the program crash detection apparatus further comprises an uploading unit configured to:
uploading program crash data to a blockchain;
and uploading the program crash data subjected to data analysis to the block chain.
In application, each unit in the program crash detection apparatus may be a software program unit, may be implemented by different logic circuits integrated in a processor or an independent physical component connected with the processor, and may also be implemented by a plurality of distributed processors.
As shown in fig. 6, an embodiment of the present application further provides a server 200, including: at least one processor 201 (only one processor is shown in fig. 6), a memory 202, and a computer program 203 stored in the memory 202 and operable on the at least one processor 201, the steps in the above-described embodiments of the program crash detection method being implemented when the computer program 203 is executed by the processor 201.
In application, the server may include but is not limited to a processor and a memory, fig. 6 is only an example of the server and does not constitute a limitation to the server, and may include more or less components than those shown, or combine some components, or different components, such as an input and output device, a network access device, and the like, and may further include a communication module, a display screen, and the like.
In an Application, the Processor may be a Central Processing Unit (CPU), and the Processor may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
In some embodiments, the storage may be an internal storage unit of the server, for example, a hard disk or a memory of the server. The memory may also be an external storage device of the server in other embodiments, for example, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. provided on the server. The memory may also include both internal storage units of the server and external storage devices. The memory is used for storing an operating system, an application program, a Boot Loader (Boot Loader), data, and other programs, such as program codes of computer programs. The memory may also be used to temporarily store data that has been output or is to be output.
In application, the Display screen may be a Thin Film Transistor Liquid Crystal Display (TFT-LCD), a Liquid Crystal Display (LCD), an Organic electroluminescent Display (OLED), a Quantum Dot Light Emitting diode (QLED) Display screen, a seven-segment or eight-segment digital tube, and the like.
In application, the Communication module may provide a solution for Communication applied to the network device, including Wireless Local Area Networks (WLANs) (such as Wi-Fi Networks), bluetooth, Zigbee, mobile Communication Networks, Global Navigation Satellite Systems (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The communication module may include an antenna, and the antenna may have only one array element, or may be an antenna array including a plurality of array elements. The communication module can receive electromagnetic waves through the antenna, frequency modulation and filtering processing are carried out on electromagnetic wave signals, and the processed signals are sent to the processor. The communication module can also receive a signal to be sent from the processor, frequency-modulate and amplify the signal, and convert the signal into electromagnetic waves through the antenna to radiate the electromagnetic waves.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/modules, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and reference may be made to the part of the embodiment of the method specifically, and details are not described here.
It will be clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely illustrated, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. Each functional module in the embodiments may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module, and the integrated module may be implemented in a form of hardware, or in a form of software functional module. In addition, specific names of the functional modules are only used for distinguishing one functional module from another, and are not used for limiting the protection scope of the present application. The specific working process of the modules in the system may refer to the corresponding process in the foregoing method embodiment, and is not described herein again.
The embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the steps in the embodiment of the program crash detection method may be implemented.
The embodiment of the present application provides a computer program product, so that when the computer program product runs on a server, the server can implement the steps in the embodiment of the program crash detection method.
The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may be stored in a computer-readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. 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 at least: any entity or device capable of carrying computer program code to a data acquisition end or client, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier wave signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims (10)

1. A method for detecting a program crash, comprising:
monitoring whether the program crash occurs to the preset program or not through a monitoring interface of a secondary packaged memory leakage detection framework;
when the preset program is crashed, generating program crash data;
and performing data analysis and data persistence on the program crash data through an external log interface of the secondary packaged memory leak detection framework.
2. The method of claim 1, wherein the monitoring interface of the memory leak detection framework that is packaged twice monitors whether a program crash occurs in a predetermined program before the monitoring interface monitors whether the program crash occurs in the predetermined program, the method comprising:
implanting a physical address for data persistence in a memory leak detection framework;
opening an external log interface of the memory leak detection framework;
pulling a source code of a preset program, and implanting a monitoring interface in a preset monitoring node in the source code of the preset program;
and configuring the configuration packet of the memory leak detection frame to the configuration packet of the source code of the preset program to finish secondary packaging of the memory leak detection frame.
3. The method of claim 2, wherein the step of configuring the configuration packet of the memory leak detection framework to the configuration packet of the source code of the predetermined program, and after completing the secondary packaging of the memory leak detection framework, further comprises:
generating a logic address of a secondary packaged memory leakage detection frame;
and configuring the logic address on a preset webpage interface, wherein the preset webpage interface is used for carrying out visual management on the memory leak detection framework.
4. The program crash detection method according to any one of claims 1 to 3, wherein the preset program comprises a security program or a futures program, and the monitoring interface comprises at least one of an ordering interface, a market query interface, a user login interface, and a user registration interface;
the external log interface comprises at least one of an inquiry interface, a filtering interface and a downloading interface.
5. The program crash detection method of any of claims 1-3, wherein the performing data parsing and data persistence on the program crash data comprises:
classifying the program crash data;
and storing the classified program crash data into a database.
6. The program crash detection method of claim 5, wherein classifying the program crash data comprises:
performing multidimensional data statistics on the program crash data of each category;
and performing multi-dimensional visualization processing on the program crash data of each category according to the dimension of the program crash data of each category.
7. The program crash detection method of claim 6, wherein the performing multidimensional data statistics on the program crash data for each category comprises:
recording the program crash data of each category according to the time and the times for monitoring the preset program;
and/or recording the program crash data of each category according to the time and the times of program crash of the preset program.
8. A program crash detection apparatus, comprising:
the monitoring unit is used for monitoring whether the program crash occurs to the preset program through a monitoring interface of the secondary packaged memory leakage detection framework;
the generating unit is used for generating program crash data when the preset program is subjected to program crash;
and the analysis unit is used for carrying out data analysis and data persistence on the program crash data through an external log interface of the secondary packaged memory leak detection framework.
9. A server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the program crash detection method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out the steps of the method for crash detection of a program according to any one of claims 1 to 7.
CN202210208459.5A 2022-03-03 2022-03-03 Program crash detection method, device, server and storage medium Pending CN114756393A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210208459.5A CN114756393A (en) 2022-03-03 2022-03-03 Program crash detection method, device, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210208459.5A CN114756393A (en) 2022-03-03 2022-03-03 Program crash detection method, device, server and storage medium

Publications (1)

Publication Number Publication Date
CN114756393A true CN114756393A (en) 2022-07-15

Family

ID=82324790

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210208459.5A Pending CN114756393A (en) 2022-03-03 2022-03-03 Program crash detection method, device, server and storage medium

Country Status (1)

Country Link
CN (1) CN114756393A (en)

Similar Documents

Publication Publication Date Title
CN110832453B (en) Distributed version control of applications using cloud-based systems
US8577904B2 (en) Composite copy and paste for composite user interfaces
US20140359129A1 (en) Migration Assessment for Cloud Computing Platforms
US8661502B2 (en) Determining a sensitivity label of document information in real time
CN112148674A (en) Log data processing method and device, computer equipment and storage medium
US20080288471A1 (en) Apparatus and method for providing a data marketplace
US20210006643A1 (en) Information display method, terminal, and server
CN113268260A (en) Routing method and device for web front end
WO2017189727A1 (en) Techniques for monitoring version numbers of web frameworks
CN111142863B (en) Page generation method and device
CN109491733B (en) Interface display method based on visualization and related equipment
CN113434582B (en) Service data processing method and device, computer equipment and storage medium
US20180069774A1 (en) Monitoring and reporting transmission and completeness of data upload from a source location to a destination location
CN115380278A (en) Object attribute dynamic verification
CN114756393A (en) Program crash detection method, device, server and storage medium
US11960476B2 (en) Techniques for concurrent data value commits
US20220198032A1 (en) Enforcing data security constraints in a data pipeline
CN118133285A (en) Vulnerability labeling method, vulnerability labeling system and device
TW202217540A (en) Mobile interface device and data filling method via the mobile interface device
CN112910874A (en) Certificate installation method and device
CN113626109A (en) Report path acquisition method and device, intelligent terminal and storage medium
CN115114337A (en) Method, device and medium for adjusting business process
CN114254621A (en) Document auditing method and device, electronic equipment and storage medium
CN118151953A (en) Application deployment method, apparatus, computer device, storage medium and program product
CN117786730A (en) Data processing method, device, equipment and storage medium

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