CN109189607A - A kind of method that application program breakpoint restores - Google Patents
A kind of method that application program breakpoint restores Download PDFInfo
- Publication number
- CN109189607A CN109189607A CN201810913285.6A CN201810913285A CN109189607A CN 109189607 A CN109189607 A CN 109189607A CN 201810913285 A CN201810913285 A CN 201810913285A CN 109189607 A CN109189607 A CN 109189607A
- Authority
- CN
- China
- Prior art keywords
- application program
- point
- event
- information recording
- pile
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
A kind of method that application program breakpoint restores.Instruction in application program is divided into relatively independent several events by this method, and driven pile point after each event.When sequentially executing the application program, the maintenance work to stake point is first carried out before one new events of every operation: the output information of the event and current stake point number and being saved to stake point information on record and is recorded in file.The operation information of application program is saved with this.When application program is run again because breaking down, first read the stake point information record file originally recorded, event of the file selection before failure generation is recorded by this point information, the application data before file acquisition failure occurs is recorded by this point information, directly restores the application program from the event.The present invention directly can restore the operation to application program from closest to the point occurred extremely in application exception as a result, and then shorten the reboot time of application program.
Description
Technical Field
The invention relates to the field of computer software and control, in particular to a breakpoint control technology of an application program.
Background
At present, if the application program needs to be re-run after an error occurs, the application program usually needs to be reloaded. The breakpoint recovery method has the following major defects and shortcomings:
① are inconvenient to use.
Each time an application is run away or the system crashes and if the code is to continue to be executed, the application must be reloaded.
② the positioning problem is difficult.
Without DEBUG information or with the aid of an external DEBUG tool or software DEBUG assistance, it is difficult for a user to locate where a problem occurs in an application if the program runs away while running.
③ consume unnecessary time and resources.
If the application is huge, the process of restarting the application inevitably repeats many unnecessary operations, and the process consumes considerable system resources or time.
④ the task restart period is long.
If the application is operating in a scene where real-time performance is highly required, the time consumed for restarting the application is likely to affect the stability of the entire software system, or the time consumed for inflating the application will have a fatal effect on the tasks performed by the application.
⑤ have a great impact on other applications running in parallel in the system.
If a running application suddenly restarts, other applications communicating with it or running in parallel may be significantly affected. The system is ensured to work normally only after the system is restarted or restarted together with the system.
Therefore, there is an urgent need for a technique for quickly recovering breakpoints of an application program, so as to reduce the restart of the application program.
Disclosure of Invention
In order to solve the defects in the prior art, the invention aims to provide a method and a system for breakpoint recovery of an application program.
Firstly, in order to achieve the above purpose, a method for restoring an application breakpoint is provided, which comprises a step of pile point creation before the application program is executed and a step of pile point maintenance in the process of executing the application program; wherein the step of stub creation prior to executing the application comprises:
a step 1, dividing the application program into mutually independent events according to the execution sequence; establishing at least two pile point information recording files, wherein pile point numbers, data information and effective flag bits are recorded in the pile point information recording files; the initial value of the stub number is the initial position of the application program, the initial value of the data information is null, and the initial value of the valid flag bit is 'no';
step a2, inserting peg points between each of the events; the pile points comprise pile point numbers, storage instructions, recovery instructions and flag bit setting instructions; the storage instruction is used for recording the current pile point number and data information into the pile point information recording file; the recovery instruction is used for reading and loading data information in the pile point information recording file; the flag bit setting instruction is used for marking the effective flag bit in the pile point information recording file as 'yes' after the storage instruction is executed;
the step of performing stub maintenance in the process of executing the application program comprises the following steps:
step b1, the application program is executed in sequence, and when the application program is executed to a stub point, the following steps are executed: executing a storage instruction in the pile point, and updating the pile point number and the data information of the pile point to a pile point information recording file updated earliest; after the storage instruction is executed, executing a flag bit setting instruction in the pile point, and updating the effective flag bit in the earliest updated pile point information recording file to be 'yes';
step b2, when the application program is abnormal, executing the following steps: searching a pile point information recording file which is updated recently and has a valid flag bit of 'yes'; jumping to the stake point corresponding to the stake point information recording file, executing a recovery instruction in the stake point, reading and loading the data information in the stake point information recording file; and continuing to execute the application programs from the stub point in sequence.
Optionally, in the method for restoring a breakpoint of an application program, the event includes one or more instructions, an execution sequence between the instructions is fixed, and the execution sequence between the instructions cannot be interrupted by other events.
Optionally, in the method for restoring a breakpoint of an application program, the data information includes: and executing the data output after the event.
Optionally, in the method for restoring a breakpoint of an application program, the data information includes data generated after each instruction in the event is executed.
Optionally, in the method for restoring a breakpoint of the application program, in the application program, according to an order from first to last in execution, the pile point numbers of the pile points are arranged from small to large, the earliest updated pile point information record file is the pile point information record file with the smallest corresponding pile point number, and the latest updated pile point information file is the pile point information record file with the largest corresponding pile point number.
Optionally, in the method for restoring a breakpoint of an application program, in the step a2, a stub point is inserted between each event specifically according to the following steps: step s1, when writing the application program into the device, reading the instructions in an event according to the execution sequence, and writing the instructions according to the execution sequence; step s2, after writing all the instructions in one event, writing the stake point corresponding to the event, where the stake point includes: a stub number, a storage instruction, a recovery instruction and a flag bit setting instruction; the stake point numbers are numbered in sequence from small to large according to the sequence of the events executed from first to last; the storage instruction calls a corresponding function according to the data type of the data information to be stored in the event so as to record the current pile point number and the data information in the pile point information recording file; the recovery instruction calls a corresponding function according to the data type of the data information needing to be read or loaded in the event so as to read and load the data information in the pile point information recording file; the flag bit setting instruction is used for marking the effective flag bit in the pile point information recording file as 'yes' after the storage instruction is executed; step s3, reading the next event according to the execution sequence, and repeating the steps s2 to s3 until all events are written.
Optionally, in the method for restoring a breakpoint of an application program, in the step a2, a stub point is inserted between each event specifically according to the following steps: step t1, when compiling the application program, dividing the application program into mutually independent events according to the execution sequence; step t2, compiling the stake point corresponding to the event after the event every time one event is compiled, wherein the stake point comprises: a stub number, a storage instruction, a recovery instruction and a flag bit setting instruction; the stake point numbers are numbered in sequence from small to large according to the sequence of the events executed from first to last; the storage instruction calls a corresponding function according to the data type of the data information to be stored in the event so as to record the current pile point number and the data information in the pile point information recording file; the recovery instruction calls a corresponding function according to the data type of the data information needing to be read or loaded in the event so as to read and load the data information in the pile point information recording file; the flag bit setting instruction is used for marking the effective flag bit in the pile point information recording file as 'yes' after the storage instruction is executed; step t3, repeating the step t2 until all events in the application program are compiled; and step t4, writing the application program to the device.
Optionally, in the method for restoring a breakpoint of an application program, the restoring instruction is stored in the stub in the form of a macro, the macro is closed when the application program is executed for the first time, the macro is opened when the application program is not executed for the first time, and the restoring instruction is not executed when the macro is closed; the macro executes the resume instruction only when turned on.
Optionally, in the method for restoring a breakpoint of an application program, in step b1, the stub information recording files are arranged from near to far according to an update sequence; in the step b2, the pile point information recording file with the first valid flag bit being "yes" is searched according to the arrangement sequence of the pile point information recording files, the pile point corresponding to the pile point information recording file is skipped to, the recovery instruction in the pile point is executed, and the data information in the pile point information recording file is read and loaded; and continuing to execute the application programs from the stub point in sequence.
Advantageous effects
The invention divides the instructions in the application program into a plurality of relatively independent events, and drives the pile point after each event. When the application program is executed in sequence, before each new event is operated, maintenance work on the stub point is carried out: and recording the output information of the event and the current stake point number and storing the output information and the current stake point number into a stake point information recording file. Thereby saving the running information of the application program. When the application program is operated again due to the occurrence of a fault, reading the originally recorded pile point information recording file, selecting the event closest to the event before the occurrence of the fault through the pile point information recording file, acquiring the application program data before the occurrence of the fault through the pile point information recording file, and directly recovering the application program from the event. Therefore, the method and the device can directly recover the operation of the application program from the point closest to the occurrence of the exception when the application program is abnormal, and further shorten the restart time of the application program.
Meanwhile, due to the action of the stub points, the application program can be ensured to automatically recover to run at the position where the fault occurs or a position slightly before the fault occurs after the fault occurs or the system is crashed. Therefore, the application program is more convenient to maintain and use. Time and resources required by the application program to run again are saved. If the application program is applied to a working scene with high real-time requirement, the method and the system can enable the application program to be rerun in the shortest time, and reduce the task restart period. The impact on software associated with restarting the application is minimized. The failed application can resume operation at the fastest speed and resume data interaction with other related processes.
In addition, due to the addition of the pile points, the application program can quickly and accurately position the error position directly according to the information in the pile point information recording file under the condition of not adding debugging information or by means of an external debugging tool or software DEBUG. The method is beneficial to the background feedback of software operation problems and the positioning of the problems.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:
FIG. 1 is a flow diagram of a method for application breakpoint recovery according to the present invention;
FIG. 2 is a diagram illustrating the execution of a resume instruction according to the present invention;
FIG. 3 is one of the execution processes of an application program to which the present invention is applied;
FIG. 4 shows a second implementation of an application to which the present invention is applied;
FIG. 5 shows a third implementation of an application to which the present invention is applied;
FIG. 6 is a fourth process of executing an application program to which the present invention is applied;
FIG. 7 shows a fifth process of executing an application program to which the present invention is applied;
FIG. 8 shows a sixth process for executing an application program to which the present invention is applied;
FIG. 9 is a schematic representation of a store instruction within a peg point in the present invention;
FIG. 10 is a schematic view of data information stored in a stub point information recording file according to the present invention;
FIG. 11 is a schematic representation of a recovery command within a stake point in the present invention;
FIG. 12 is an example of a function called by the resume instruction according to the data type of the data information in the event according to the present invention.
Detailed Description
The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it will be understood that they are described herein for the purpose of illustration and explanation and not limitation.
FIG. 1 is a flowchart of a method for breakpoint restoration of an application program according to the present invention, including a step of stub creation before executing the application program and a step of stub maintenance during executing the application program;
wherein the step of stub creation prior to executing the application comprises:
a step 1, dividing the application program into mutually independent events according to the execution sequence; establishing at least two pile point information recording files, wherein pile point numbers, data information and effective flag bits are recorded in the pile point information recording files; the initial value of the stub number is the initial position of the application program, the initial value of the data information is null, and the initial value of the valid flag bit is 'no';
step a2, inserting peg points between each of the events; the pile points comprise pile point numbers, storage instructions, recovery instructions and flag bit setting instructions; the storage instruction is used for recording the current pile point number and data information into the pile point information recording file; the recovery instruction is used for reading and loading data information in the pile point information recording file; the flag bit setting instruction is used for marking the effective flag bit in the pile point information recording file as 'yes' after the storage instruction is executed;
the step of performing stub maintenance in the process of executing the application program comprises the following steps:
step b1, the application program is executed in sequence, and when the application program is executed to a stub point, the following steps are executed: executing a storage instruction in the pile point, and updating the pile point number and the data information of the pile point to a pile point information recording file updated earliest; after the storage instruction is executed, executing a flag bit setting instruction in the pile point, and updating the effective flag bit in the earliest updated pile point information recording file to be 'yes';
step b2, when the application program is abnormal, executing the following steps: searching a pile point information recording file which is updated recently and has a valid flag bit of 'yes'; jumping to the stake point corresponding to the stake point information recording file, executing a recovery instruction in the stake point, reading and loading the data information in the stake point information recording file; and continuing to execute the application programs from the stub point in sequence.
Here, the event non-detachable means that the event cannot be interrupted by external objects during the execution process of the event, and if the event is interrupted, the event needs to be executed again. For example: if the temperature of the temperature sensor needs to be acquired, the temperature value can be acquired after the temperature sensor is subjected to relevant initial configuration operation. Therefore, the event consisting of initializing the temperature sensor and acquiring the temperature value is an inseparable event. Example 2, if the average value of 10 temperature data needs to be calculated, 10 temperature data needs to be extracted first and recorded in corresponding variables for calculation, so that the extraction of 10 temperature values and calculation constitute an uninterruptible event.
The following describes the execution of the method by taking the application program shown in fig. 3 as an example.
In fig. 3, when the application starts executing, the application first detects whether there are two stub information recording files, if not, it indicates that the application is executed for the first time, and creates two stub information recording files (the specific flow is shown in fig. 3). The file content contains 2 parts: the first part is the pile point number after execution, and the default initial value is the initial segment. The second part is the value output after the event is completed, and is divided into Save segment and recovery segment at each stake point as shown in fig. 3. The Save section comprises a storage instruction, and the function of the storage instruction is to record data information to be saved into the information recording file. The recovery section includes a recovery instruction, and functions to read corresponding data from the information recording file and Recover corresponding variables. When the application program runs normally, the Save section in the stub point is executed every time an event is run, and the output value of each event is saved in a configuration file. After the output information is saved, the application program skips the recovery section to continue executing the next event. When the application program runs again when encountering faults, the recovery section is executed to the corresponding stub point according to the information in the configuration file, and the output value of the last successful execution event is recovered. After the data recovery is finished, the application program jumps to the next event to continue to execute the next event, and after the execution is finished, the Save section of the stake point corresponding to the next event is continuously executed to Save the data and not execute the recovery section until the next program is restarted due to a fault.
As shown in fig. 4, when the application finishes executing the event 1 and reaches the stub 2, the data that needs to be saved by the event 1 is written into the file 1, and then the executed stub number is updated to the stub unit and the effective flag bit of the stub is set. If the program fails to cause the program to operate again, the effective mark bit of the stub point is read firstly before the configuration file is loaded, and if the mark bit is not set, the program fails when the configuration file is updated, and the information in another configuration file needs to be read to obtain effective information. The reason for choosing to save data with two configuration files is to ensure that a failure occurs during the write operation to one configuration file, and valid information for program recovery is still saved in the other configuration file. As shown in fig. 10, the user needs to select a corresponding Save function in the Save section of the corresponding stub point and fill in the corresponding parameter to Save the data to be saved into the information recording file. As shown in fig. 9, taking the data to be saved in peg 1 as an example, the final data will be converted into the corresponding character string and written into the corresponding information recording file. Before saving data, the whole file is traversed to inquire whether the information of the corresponding variable is saved before, if so, the value of the corresponding variable in the file is directly updated, otherwise, the variable information is directly written into the corresponding file.
As shown in fig. 5, when the application finishes executing the event 2 and reaches the stub 3, the data that needs to be saved by the event 2 is saved in the file 2, and then the executed stub number is updated to the stub unit and the effective flag bit of the stub is set. The two stub point information recording files sequentially and alternately record the execution condition of the application program so as to ensure that at least one recording file can correctly store the data information and the position of the operation of the application program.
Preferably, after the program finishes an event, when the stub information recording file is updated, the information in the original stub information recording file can be overwritten, so as to avoid the file from being too large.
As shown in fig. 6, when the application runs at event 3, the system suddenly goes down or cannot continue to run for other reasons, and the operation of writing the log file is not triggered.
When the application program runs again as shown in fig. 7, whether two pile point information recording files exist is detected, and if so, pile point numbers in the two files are sequentially read for comparison and the pile point validity is judged. The specific flow of selecting the larger number of the effective stakes (if the number of the stakes in the two files is the same, the information in the file 1 is selected) is shown in fig. 2.
As shown in fig. 8, after the program jumps to the designated recovery stub, a recovery function filled by the user before is called (the specific function is shown in fig. 11), and taking fig. 12 as an example, by calling the corresponding function to retrieve the stored data in the file, reading the corresponding length, converting the character string into the corresponding number or other value, and reassigning the character string to the variable corresponding to the application program. After the assignment is completed, the program will continue to execute the corresponding event as shown in fig. 8.
The technical scheme of the invention has the advantages that:
the invention provides a new mechanism for breakpoint operation of an application program, which is suitable for a general software platform. The method not only reduces the time for restarting and operating the program, but also facilitates the programmer to accurately position the position where the problem occurs in time. The reason is mainly that:
the invention divides the existing application program into corresponding events, and each event is not detachable. The invention fills the running state recording mechanism in the middle of each event. After the application program successfully runs an event, the running state recording mechanism updates the flag set of each event running success, saves the data required to be saved by the corresponding event, and writes the data into the corresponding stub point information recording file.
When the program runs away or the system crashes to cause the application program to restart. The application program can read the position where the application program is executed successfully at last according to the corresponding pile point information recording file generated before, and reads the corresponding data from the corresponding log file for recovery before jumping to the event which is not executed successfully. Execution continues after recovery is complete.
By the mechanism for recording the running state of the application program, the efficiency of rerun of the application program after running errors can be greatly improved. When errors repeatedly occur, a programmer can timely and accurately locate the position of the cause of the problem by checking the configuration file.
Those of ordinary skill in the art will understand that: although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that changes may be made in the embodiments and/or equivalents thereof without departing from the spirit and scope of the invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. A method for restoring breakpoints of an application program is characterized by comprising the steps of pile point creation before the application program is executed and pile point maintenance in the process of executing the application program; wherein,
the step of stub creation prior to executing the application program comprises:
a step 1, dividing the application program into mutually independent events according to the execution sequence; establishing at least two pile point information recording files, wherein pile point numbers, data information and effective flag bits are recorded in the pile point information recording files; the initial value of the stub number is the initial position of the application program, the initial value of the data information is null, and the initial value of the valid flag bit is 'no';
step a2, inserting peg points between each of the events; the pile points comprise pile point numbers, storage instructions, recovery instructions and flag bit setting instructions; the storage instruction is used for recording the current pile point number and data information into the pile point information recording file; the recovery instruction is used for reading and loading data information in the pile point information recording file; the flag bit setting instruction is used for marking the effective flag bit in the pile point information recording file as 'yes' after the storage instruction is executed;
the step of performing stub maintenance in the process of executing the application program comprises the following steps:
step b1, the application program is executed in sequence, and when the application program is executed to a stub point, the following steps are executed: executing a storage instruction in the pile point, and updating the pile point number and the data information of the pile point to a pile point information recording file updated earliest; after the storage instruction is executed, executing a flag bit setting instruction in the pile point, and updating the effective flag bit in the earliest updated pile point information recording file to be 'yes';
step b2, when the application program is abnormal, executing the following steps: searching a pile point information recording file which is updated recently and has a valid flag bit of 'yes'; jumping to the stake point corresponding to the stake point information recording file, executing a recovery instruction in the stake point, reading and loading the data information in the stake point information recording file; and continuing to execute the application programs from the stub point in sequence.
2. A method of application breakpoint recovery as claimed in claim 1, wherein the events include one or more instructions, the execution order between the instructions is fixed and the execution order between the instructions is not interruptible by other events.
3. A method of application breakpoint recovery as recited in claim 1, wherein the data information includes: and executing the data output after the event.
4. A method of application breakpoint restoration according to claim 3, wherein the data information comprises data generated upon execution of each of the instructions of the event.
5. The method for restoring a breakpoint of an application program according to claim 1, wherein, in the application program, in order from first to last in execution, the stake point numbers of the stake points are arranged from small to large, the stake point information record file updated earliest is the stake point information record file with the smallest corresponding stake point number, and the stake point information file updated latest is the stake point information record file with the largest corresponding stake point number.
6. The method for restoring the breakpoint of the application program according to claims 1 to 5, wherein in the step a2, a stub point is inserted between each event according to the following steps:
step s1, when writing the application program into the device, reading the instructions in an event according to the execution sequence, and writing the instructions according to the execution sequence;
step s2, after writing all the instructions in one event, writing the stake point corresponding to the event, where the stake point includes: a stub number, a storage instruction, a recovery instruction and a flag bit setting instruction; the stake point numbers are numbered in sequence from small to large according to the sequence of the events executed from first to last; the storage instruction calls a corresponding function according to the data type of the data information to be stored in the event so as to record the current pile point number and the data information in the pile point information recording file; the recovery instruction calls a corresponding function according to the data type of the data information needing to be read or loaded in the event so as to read and load the data information in the pile point information recording file; the flag bit setting instruction is used for marking the effective flag bit in the pile point information recording file as 'yes' after the storage instruction is executed;
step s3, reading the next event according to the execution sequence, and repeating the steps s2 to s3 until all events are written.
7. The method for restoring the breakpoint of the application program according to claims 1 to 5, wherein in the step a2, a stub point is inserted between each event according to the following steps:
step t1, when compiling the application program, dividing the application program into mutually independent events according to the execution sequence;
step t2, compiling the stake point corresponding to the event after the event every time one event is compiled, wherein the stake point comprises: a stub number, a storage instruction, a recovery instruction and a flag bit setting instruction; the stake point numbers are numbered in sequence from small to large according to the sequence of the events executed from first to last; the storage instruction calls a corresponding function according to the data type of the data information to be stored in the event so as to record the current pile point number and the data information in the pile point information recording file; the recovery instruction calls a corresponding function according to the data type of the data information needing to be read or loaded in the event so as to read and load the data information in the pile point information recording file; the flag bit setting instruction is used for marking the effective flag bit in the pile point information recording file as 'yes' after the storage instruction is executed;
step t3, repeating the step t2 until all events in the application program are compiled;
and step t4, writing the application program to the device.
8. The method for breakpoint restoration of an application program according to claims 6 to 7, wherein the restoration instruction is stored in the stub in the form of a macro, the macro is closed when the application program is executed for the first time, the macro is opened when the application program is not executed for the first time,
not executing the resume instruction when the macro is turned off; the macro executes the resume instruction only when turned on.
9. The method for restoring the breakpoint of the application program according to claims 6 to 7, wherein in the step b1, the stub information recording files are arranged from near to far according to the updating sequence;
in the step b2, the pile point information recording file with the first valid flag bit being "yes" is searched according to the arrangement sequence of the pile point information recording files, the pile point corresponding to the pile point information recording file is skipped to, the recovery instruction in the pile point is executed, and the data information in the pile point information recording file is read and loaded; and continuing to execute the application programs from the stub point in sequence.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810913285.6A CN109189607B (en) | 2018-08-13 | 2018-08-13 | Method for restoring breakpoint of application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810913285.6A CN109189607B (en) | 2018-08-13 | 2018-08-13 | Method for restoring breakpoint of application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109189607A true CN109189607A (en) | 2019-01-11 |
| CN109189607B CN109189607B (en) | 2020-08-04 |
Family
ID=64921554
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810913285.6A Active CN109189607B (en) | 2018-08-13 | 2018-08-13 | Method for restoring breakpoint of application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109189607B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112099993A (en) * | 2020-09-16 | 2020-12-18 | 福建天晴在线互动科技有限公司 | Method and system for recovering field after program abnormal exit |
| CN114065493A (en) * | 2021-11-04 | 2022-02-18 | 中国核动力研究设计院 | Method and system for optimizing stability of analysis program of reactor system |
| WO2022267812A1 (en) * | 2021-06-23 | 2022-12-29 | 中兴通讯股份有限公司 | Software recovery method, electronic device, and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060200482A1 (en) * | 2005-03-07 | 2006-09-07 | International Business Machines Corporation | System, Method and Program Product for Setting and Managing Breakpoints in a Data Schema Mapping Editor |
| US7185321B1 (en) * | 2002-03-29 | 2007-02-27 | Cypress Semiconductor Corporation | Method and system for debugging through supervisory operating codes and self modifying codes |
| CN103645961A (en) * | 2013-11-20 | 2014-03-19 | 清华大学 | Anomaly detection method and system for calculating intensive parallel tasks |
| CN104598274A (en) * | 2015-01-13 | 2015-05-06 | 北京京东尚科信息技术有限公司 | Automatic instrumentation, compiling and installing method and system |
| CN105260312A (en) * | 2015-10-26 | 2016-01-20 | 北京航空航天大学 | Debugging method for multi-core real-time system application data race errors |
| CN108090346A (en) * | 2017-12-04 | 2018-05-29 | 华中科技大学 | A kind of code reuse attack defense method and system based on data stream monitoring |
-
2018
- 2018-08-13 CN CN201810913285.6A patent/CN109189607B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7185321B1 (en) * | 2002-03-29 | 2007-02-27 | Cypress Semiconductor Corporation | Method and system for debugging through supervisory operating codes and self modifying codes |
| US20060200482A1 (en) * | 2005-03-07 | 2006-09-07 | International Business Machines Corporation | System, Method and Program Product for Setting and Managing Breakpoints in a Data Schema Mapping Editor |
| CN103645961A (en) * | 2013-11-20 | 2014-03-19 | 清华大学 | Anomaly detection method and system for calculating intensive parallel tasks |
| CN104598274A (en) * | 2015-01-13 | 2015-05-06 | 北京京东尚科信息技术有限公司 | Automatic instrumentation, compiling and installing method and system |
| CN105260312A (en) * | 2015-10-26 | 2016-01-20 | 北京航空航天大学 | Debugging method for multi-core real-time system application data race errors |
| CN108090346A (en) * | 2017-12-04 | 2018-05-29 | 华中科技大学 | A kind of code reuse attack defense method and system based on data stream monitoring |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112099993A (en) * | 2020-09-16 | 2020-12-18 | 福建天晴在线互动科技有限公司 | Method and system for recovering field after program abnormal exit |
| CN112099993B (en) * | 2020-09-16 | 2023-06-30 | 福建天晴在线互动科技有限公司 | Method and system for recovering field after program exception exit |
| WO2022267812A1 (en) * | 2021-06-23 | 2022-12-29 | 中兴通讯股份有限公司 | Software recovery method, electronic device, and storage medium |
| CN114065493A (en) * | 2021-11-04 | 2022-02-18 | 中国核动力研究设计院 | Method and system for optimizing stability of analysis program of reactor system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109189607B (en) | 2020-08-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6874138B1 (en) | Method and apparatus for resuming execution of a failed computer program | |
| CN103116532B (en) | Damage in fault from the storehouse embedded software system and recover | |
| CN109189607B (en) | Method for restoring breakpoint of application program | |
| CN101344868B (en) | Data backup and acquiring method and device | |
| KR100744873B1 (en) | How to record firmware on a computer system | |
| CN104239082A (en) | Hot patching implementation method of embedded system | |
| CN109032838B (en) | Automatic verification method for consistency of backup and recovery data of virtual machine | |
| JP2000020349A (en) | Program development support device, program development support method, and medium recording program development support program | |
| CN116909607A (en) | Program upgrading method, program upgrading device, computer equipment, storage medium and program product | |
| CN115620799A (en) | Firmware simulation-based fault site backtracking method and equipment and readable storage medium | |
| CN113157519A (en) | Embedded computer system fault auxiliary positioning architecture and method | |
| CN110362432B (en) | Backup method, device, equipment and storage medium | |
| CN108733567A (en) | The monitoring method and system of software resource leak case | |
| CN105988885B (en) | Operating system failure self-recovery method based on compensation rollback | |
| CN117785554A (en) | Device power-down data retention method, system, device and readable storage medium | |
| JP4155052B2 (en) | Emulator, emulation method and program | |
| CN116627519A (en) | Multisystem starting method of embedded equipment | |
| CN113986587A (en) | Method, system, storage medium and device for implementing checkpoint based on value log | |
| CN117724658B (en) | Data security storage method and system based on embedded Linux system | |
| CN100458719C (en) | Method and system for acquiring and editing basic input and output system information | |
| CN116028128B (en) | Disk partition storage method, operating system automatic recovery method and storage medium | |
| CN116737089B (en) | Configuration data storage methods, devices and systems | |
| CN1194296C (en) | How to replace the firmware of the computer system | |
| CN118800314B (en) | A memory and abnormality positioning method thereof | |
| CN109739774A (en) | EDAC direct fault location and detection method |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |