CN114238098A - Embedded software stack use condition dynamic analysis method and system based on data breakpoint - Google Patents
Embedded software stack use condition dynamic analysis method and system based on data breakpoint Download PDFInfo
- Publication number
- CN114238098A CN114238098A CN202111501263.7A CN202111501263A CN114238098A CN 114238098 A CN114238098 A CN 114238098A CN 202111501263 A CN202111501263 A CN 202111501263A CN 114238098 A CN114238098 A CN 114238098A
- Authority
- CN
- China
- Prior art keywords
- program
- analyzed
- stack
- analysis
- embedded
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004458 analytical method Methods 0.000 title claims abstract description 112
- 230000002159 abnormal effect Effects 0.000 claims abstract description 31
- 238000000034 method Methods 0.000 claims abstract description 19
- 238000012545 processing Methods 0.000 claims abstract description 14
- 230000006870 function Effects 0.000 description 31
- 230000003068 static effect Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/72—Code refactoring
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a dynamic analysis method and a dynamic analysis system for use conditions of an embedded software stack based on data breakpoints, which comprise the following steps: step 1: compiling the analyzed program, and calling an analysis starting interface at a preset position; step 2: acquiring a preset stack space of a current embedded program through a preset analysis module, setting a data breakpoint for the preset stack space, and enabling the data breakpoint of the embedded target board to be abnormal; and step 3: in the abnormal processing of the data breakpoint, analyzing a target address read or modified by a current instruction, and recording the target address; and 4, step 4: and when the analyzed program runs to a preset position, calling an analysis ending interface, closing the data breakpoint exception of the target board and outputting a stack analysis result. The invention realizes the dynamic analysis of the stack use condition of the embedded program in the running process of the embedded program under the conditions of not inserting source codes and not using a simulator.
Description
Technical Field
The invention relates to the technical field of embedded software, in particular to a method and a system for dynamically analyzing the use condition of an embedded software stack based on data breakpoints.
Background
Currently, there are two general use cases for embedded software stacks:
static analysis: analyzing the stack use condition of the embedded software in a static mode by using a source code or a disassembly code of the embedded software;
dynamic analysis: the stack use condition of the embedded software is periodically and dynamically detected by starting a system timer and the like.
Patent document CN110096888B (application number: CN201910311605.5) discloses a method and system for accelerating the verification and analysis of SMM security risks, the method comprising: deploying a basic environment, acquiring and recording host environment information, and acquiring a visual bios source code calling relation graph and a module composition graph of a bios mirror image; acquiring a GUID (unique identifier) related to an SMM (SMM), and matching the GUID related to the SMM in a bios source code with a corresponding GUID in a bin mirror image generated by compiling the source code; acquiring environment information of a virtual machine, and setting calling stack information during breakpoint capture operation; and verifying and analyzing the potential safety hazard of the SMM.
With the rapid development of computer technology, the embedded system is not only more and more widely applied in daily life of people, but also plays an increasingly critical role in some high-end fields such as aviation and military related control fields, the requirements on the safety and stability of embedded software in the related fields are also continuously improved, C language is used as the most extensive programming language in the embedded software, and a plurality of potential safety hazards, particularly potential stack overflow hazards exist.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a method and a system for dynamically analyzing the use condition of an embedded software stack based on data breakpoints.
The embedded software stack use condition dynamic analysis method based on the data breakpoint provided by the invention comprises the following steps:
step 1: compiling the analyzed program, and calling an analysis starting interface at a preset position;
step 2: acquiring a preset stack space of a current embedded program through a preset analysis module, setting a data breakpoint for the preset stack space, and enabling the data breakpoint of the embedded target board to be abnormal;
and step 3: in the abnormal processing of the data breakpoint, analyzing a target address read or modified by a current instruction, and recording the target address;
and 4, step 4: and when the analyzed program runs to a preset position, calling an analysis ending interface, closing the data breakpoint exception of the target board and outputting a stack analysis result.
Preferably, the source code of the analyzed program is modified, an analysis start function and an analysis end function of the preset analysis module are respectively called at a start point and an end point of an analysis range of the analyzed program, and then the modified embedded program is compiled according to the original compiling mode to generate the executable embedded program.
Preferably, downloading and solidifying the recompiled embedded program, and running the analyzed embedded program;
when the embedded program to be analyzed runs to the analysis starting function, acquiring a preset stack space of the program to be analyzed according to a stack starting label and a stack ending label in a compiling link script of the program, setting a data breakpoint aiming at the preset stack space of the program to be analyzed, enabling the data breakpoint to be abnormal, triggering the data breakpoint to be abnormal when the program to be analyzed is subjected to a stack pushing or stack pulling operation in the running process, and simultaneously mounting an interrupt processing function with the abnormal data breakpoint in a preset analysis module into the embedded program to be analyzed.
Preferably, after the analyzed embedded program generates a data breakpoint exception, an operation target address of the current instruction is analyzed in an exception handling function of the data breakpoint exception, where the target address is an operation address of the current stack pointer, and the target address is recorded at the same time.
Preferably, when the embedded program to be analyzed is executed to the analysis ending function, the data breakpoint abnormity is closed through the preset analysis module, and the recording result is analyzed and then the actual use condition of the stack space is output.
The embedded software stack use condition dynamic analysis system based on the data breakpoint provided by the invention comprises the following components:
module M1: compiling the analyzed program, and calling an analysis starting interface at a preset position;
module M2: acquiring a preset stack space of a current embedded program through a preset analysis module, setting a data breakpoint for the preset stack space, and enabling the data breakpoint of the embedded target board to be abnormal;
module M3: in the abnormal processing of the data breakpoint, analyzing a target address read or modified by a current instruction, and recording the target address;
module M4: and when the analyzed program runs to a preset position, calling an analysis ending interface, closing the data breakpoint exception of the target board and outputting a stack analysis result.
Preferably, the source code of the analyzed program is modified, an analysis start function and an analysis end function of the preset analysis module are respectively called at a start point and an end point of an analysis range of the analyzed program, and then the modified embedded program is compiled according to the original compiling mode to generate the executable embedded program.
Preferably, downloading and solidifying the recompiled embedded program, and running the analyzed embedded program;
when the embedded program to be analyzed runs to the analysis starting function, acquiring a preset stack space of the program to be analyzed according to a stack starting label and a stack ending label in a compiling link script of the program, setting a data breakpoint aiming at the preset stack space of the program to be analyzed, enabling the data breakpoint to be abnormal, triggering the data breakpoint to be abnormal when the program to be analyzed is subjected to a stack pushing or stack pulling operation in the running process, and simultaneously mounting an interrupt processing function with the abnormal data breakpoint in a preset analysis module into the embedded program to be analyzed.
Preferably, after the analyzed embedded program generates a data breakpoint exception, an operation target address of the current instruction is analyzed in an exception handling function of the data breakpoint exception, where the target address is an operation address of the current stack pointer, and the target address is recorded at the same time.
Preferably, when the embedded program to be analyzed is executed to the analysis ending function, the data breakpoint abnormity is closed through the preset analysis module, and the recording result is analyzed and then the actual use condition of the stack space is output.
Compared with the prior art, the invention has the following beneficial effects:
the method realizes the dynamic analysis of the stack use condition of the embedded program in the running process of the embedded program under the conditions of not inserting the source code and not depending on a simulator, and has certain practical application value in the embedded software evaluation in the field of high safety and reliability; and record analysis is carried out every time the stack space is modified, so that the analysis result is more accurate.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments with reference to the following drawings:
FIG. 1 is a flow chart of the relationship between the analyzed program and the analysis module and the execution of the program;
FIG. 2 is a flow chart of the compilation of the analysis module and the analyzed program.
Detailed Description
The present invention will be described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the invention, but are not intended to limit the invention in any way. It should be noted that it would be obvious to those skilled in the art that various changes and modifications can be made without departing from the spirit of the invention. All falling within the scope of the present invention.
Example (b):
as shown in fig. 1 and fig. 2, the present invention provides a dynamic analysis method for use condition of an embedded software stack based on data breakpoints, including:
the analysis module is compiled together with the analyzed program, an analysis starting interface is called at the position designated by the analyzed program, the analysis module acquires the preset stack space of the current embedded program, a data breakpoint is set for the preset stack space of the program, and the data breakpoint abnormity of the embedded target board is enabled. In exception handling of data breakpoints, the target address to be accessed (read or modified) by the current instruction is analyzed and recorded. And when the analyzed program runs to the analysis ending interface, closing the data breakpoint exception of the target board and outputting a stack analysis result.
The method can perform dynamic analysis on the stack use condition of the embedded software without instrumentation of source codes and by means of a simulator, and because the dynamic analysis is performed in the actual running process of the embedded program, the analysis result is more reliable than static analysis based on a dataflow graph. The method comprises the following steps:
1. firstly, source codes of an analyzed program are modified, an analysis starting function and an analysis ending function of an analysis module are respectively called at a starting point and an ending point of an analysis range of the analyzed program, referring to fig. 1, and then the modified embedded program is compiled according to an original compiling mode to generate an executable embedded program.
2. Downloading or solidifying the recompiled embedded program and running the analyzed embedded program.
3. When the embedded program to be analyzed runs to the analysis starting function, the analysis starting function acquires a preset stack space of the program to be analyzed according to the compiling and linking information (a stack starting label and a stack ending label in a linking script) of the program to be analyzed, and sets a data breakpoint (according to the definition of the data breakpoint, the data breakpoint can set a section of address range, and any access of a processor to the address range can trigger the data breakpoint to be abnormal) aiming at the preset stack space of the program to be analyzed, so that the data breakpoint can be abnormal, and the data breakpoint can be triggered to be abnormal when the program to be analyzed is subjected to stack pushing or stack pulling operation in the running process. And simultaneously, the analysis starting function mounts the interrupt processing function with abnormal data breakpoints in the analysis module into the interrupt processing module of the analyzed embedded program.
4. After the embedded program to be analyzed generates the data breakpoint exception, the operation target address of the current instruction is analyzed in the exception handling function of the data breakpoint exception (the interrupt handling function of the analysis module), because the interrupt handling function is already mounted in the interrupt handling module of the embedded program to be analyzed in the analysis starting function, the processor will automatically execute the interrupt handling function when the data breakpoint exception is generated, and the target address is the operation address of the current stack pointer and is recorded at the same time.
5. And when the embedded program to be analyzed is executed to the analysis ending function, the analysis module closes the data breakpoint abnormity, and outputs the actual use condition of the stack space after analyzing the recording result of the step 4.
The embedded software stack use condition dynamic analysis system based on the data breakpoint provided by the invention comprises the following components: module M1: compiling the analyzed program, and calling an analysis starting interface at a preset position; module M2: acquiring a preset stack space of a current embedded program through a preset analysis module, setting a data breakpoint for the preset stack space, and enabling the data breakpoint of the embedded target board to be abnormal; module M3: in the abnormal processing of the data breakpoint, analyzing a target address read or modified by a current instruction, and recording the target address; module M4: and when the analyzed program runs to a preset position, calling an analysis ending interface, closing the data breakpoint exception of the target board and outputting a stack analysis result.
Modifying the source code of the analyzed program, calling an analysis starting function and an analysis ending function of a preset analysis module at the starting point and the ending point of the analysis range of the analyzed program respectively, and compiling the modified embedded program according to the original compiling mode to generate the executable embedded program. Downloading and solidifying the recompiled embedded program, and running the analyzed embedded program; when the embedded program to be analyzed runs to the analysis starting function, acquiring a preset stack space of the program to be analyzed according to a stack starting label and a stack ending label in a compiling link script of the program, setting a data breakpoint aiming at the preset stack space of the program to be analyzed, enabling the data breakpoint to be abnormal, triggering the data breakpoint to be abnormal when the program to be analyzed is subjected to a stack pushing or stack pulling operation in the running process, and simultaneously mounting an interrupt processing function with the abnormal data breakpoint in a preset analysis module into the embedded program to be analyzed. After the embedded program to be analyzed generates data breakpoint abnormity, analyzing the operation target address of the current instruction in an abnormity processing function of the data breakpoint abnormity, wherein the target address is the operation address of the current stack pointer, and simultaneously recording the target address. And when the embedded program to be analyzed is executed to the analysis ending function, closing the data breakpoint abnormity through the preset analysis module, analyzing the recording result and outputting the actual use condition of the stack space.
Those skilled in the art will appreciate that, in addition to implementing the systems, apparatus, and various modules thereof provided by the present invention in purely computer readable program code, the same procedures can be implemented entirely by logically programming method steps such that the systems, apparatus, and various modules thereof are provided in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Therefore, the system, the device and the modules thereof provided by the present invention can be considered as a hardware component, and the modules included in the system, the device and the modules thereof for implementing various programs can also be considered as structures in the hardware component; modules for performing various functions may also be considered to be both software programs for performing the methods and structures within hardware components.
The foregoing description of specific embodiments of the present invention has been presented. It is to be understood that the present invention is not limited to the specific embodiments described above, and that various changes or modifications may be made by one skilled in the art within the scope of the appended claims without departing from the spirit of the invention. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.
Claims (10)
1. A dynamic analysis method for embedded software stack use condition based on data breakpoint is characterized by comprising the following steps:
step 1: compiling the analyzed program, and calling an analysis starting interface at a preset position;
step 2: acquiring a preset stack space of a current embedded program through a preset analysis module, setting a data breakpoint for the preset stack space, and enabling the data breakpoint of the embedded target board to be abnormal;
and step 3: in the abnormal processing of the data breakpoint, analyzing a target address read or modified by a current instruction, and recording the target address;
and 4, step 4: and when the analyzed program runs to a preset position, calling an analysis ending interface, closing the data breakpoint exception of the target board and outputting a stack analysis result.
2. The embedded software stack use condition dynamic analysis method based on single-step exception as claimed in claim 1, characterized in that the source code of the analyzed program is modified, the analysis start function and the analysis end function of the preset analysis module are respectively called at the start point and the end point of the analysis range of the analyzed program, and then the modified embedded program is compiled according to the original compiling mode to generate the executable embedded program.
3. The embedded software stack use condition dynamic analysis method based on single-step exception as claimed in claim 2, characterized in that the recompiled embedded program is downloaded and solidified, and the analyzed embedded program is run;
when the embedded program to be analyzed runs to the analysis starting function, acquiring a preset stack space of the program to be analyzed according to a stack starting label and a stack ending label in a compiling link script of the program, setting a data breakpoint aiming at the preset stack space of the program to be analyzed, enabling the data breakpoint to be abnormal, triggering the data breakpoint to be abnormal when the program to be analyzed is subjected to a stack pushing or stack pulling operation in the running process, and simultaneously mounting an interrupt processing function with the abnormal data breakpoint in a preset analysis module into the embedded program to be analyzed.
4. The embedded software stack usage dynamic analysis method based on single-step exception as recited in claim 3, wherein after the analyzed embedded program generates the data breakpoint exception, the operating target address of the current instruction is analyzed in the exception handling function of the data breakpoint exception, the target address is the operating address of the current stack pointer, and the target address is recorded at the same time.
5. The embedded software stack use condition dynamic analysis method based on single-step exception as recited in claim 4, characterized in that when the embedded program to be analyzed is executed to the analysis end function, the data breakpoint exception is closed through the preset analysis module, and the recorded result is analyzed and then the actual use condition of the stack space is output.
6. A dynamic analysis system for embedded software stack use condition based on data breakpoint is characterized by comprising:
module M1: compiling the analyzed program, and calling an analysis starting interface at a preset position;
module M2: acquiring a preset stack space of a current embedded program through a preset analysis module, setting a data breakpoint for the preset stack space, and enabling the data breakpoint of the embedded target board to be abnormal;
module M3: in the abnormal processing of the data breakpoint, analyzing a target address read or modified by a current instruction, and recording the target address;
module M4: and when the analyzed program runs to a preset position, calling an analysis ending interface, closing the data breakpoint exception of the target board and outputting a stack analysis result.
7. The embedded software stack usage situation dynamic analysis system based on single-step exception as claimed in claim 6, wherein the source code of the analyzed program is modified, the analysis start function and the analysis end function of the preset analysis module are respectively called at the start point and the end point of the analysis range of the analyzed program, and then the modified embedded program is compiled according to its original compiling mode to generate the executable embedded program.
8. The single-step exception based embedded software stack usage dynamic analysis system of claim 7, wherein the recompiled embedded program is downloaded and cured and the analyzed embedded program is run;
when the embedded program to be analyzed runs to the analysis starting function, acquiring a preset stack space of the program to be analyzed according to a stack starting label and a stack ending label in a compiling link script of the program, setting a data breakpoint aiming at the preset stack space of the program to be analyzed, enabling the data breakpoint to be abnormal, triggering the data breakpoint to be abnormal when the program to be analyzed is subjected to a stack pushing or stack pulling operation in the running process, and simultaneously mounting an interrupt processing function with the abnormal data breakpoint in a preset analysis module into the embedded program to be analyzed.
9. The embedded software stack usage dynamic analysis system based on single-step exception as recited in claim 8, wherein after the analyzed embedded program generates the data breakpoint exception, the operating target address of the current instruction is analyzed in the exception handling function of the data breakpoint exception, and the target address is the operating address of the current stack pointer and is recorded at the same time.
10. The embedded software stack use condition dynamic analysis system based on single-step exception as recited in claim 9, wherein when the embedded program to be analyzed is executed to the analysis end function, the data breakpoint exception is closed through the preset analysis module, and the recorded result is analyzed and then the actual use condition of the stack space is output.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111501263.7A CN114238098A (en) | 2021-12-09 | 2021-12-09 | Embedded software stack use condition dynamic analysis method and system based on data breakpoint |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111501263.7A CN114238098A (en) | 2021-12-09 | 2021-12-09 | Embedded software stack use condition dynamic analysis method and system based on data breakpoint |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114238098A true CN114238098A (en) | 2022-03-25 |
Family
ID=80754402
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111501263.7A Pending CN114238098A (en) | 2021-12-09 | 2021-12-09 | Embedded software stack use condition dynamic analysis method and system based on data breakpoint |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114238098A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1752946A (en) * | 2005-10-31 | 2006-03-29 | 大唐微电子技术有限公司 | Debugging method of embedded system and its system |
| CN104063319A (en) * | 2014-06-26 | 2014-09-24 | 上海凌阳科技有限公司 | Debugging method of embedded system and device thereof |
| CN110096888A (en) * | 2019-04-18 | 2019-08-06 | 苏州浪潮智能科技有限公司 | A kind of method and system for accelerating verifying and analysis SMM security risk |
| CN113111001A (en) * | 2021-04-29 | 2021-07-13 | 苏州大学 | Remote software debugging method for embedded terminal |
| CN113742119A (en) * | 2021-07-26 | 2021-12-03 | 上海闻泰信息技术有限公司 | Call stack backtracking method and device of embedded system and computer equipment |
| CN113742237A (en) * | 2021-09-13 | 2021-12-03 | 北京奕斯伟计算技术有限公司 | Program debugging method, device, equipment and storage medium |
-
2021
- 2021-12-09 CN CN202111501263.7A patent/CN114238098A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1752946A (en) * | 2005-10-31 | 2006-03-29 | 大唐微电子技术有限公司 | Debugging method of embedded system and its system |
| CN104063319A (en) * | 2014-06-26 | 2014-09-24 | 上海凌阳科技有限公司 | Debugging method of embedded system and device thereof |
| CN110096888A (en) * | 2019-04-18 | 2019-08-06 | 苏州浪潮智能科技有限公司 | A kind of method and system for accelerating verifying and analysis SMM security risk |
| CN113111001A (en) * | 2021-04-29 | 2021-07-13 | 苏州大学 | Remote software debugging method for embedded terminal |
| CN113742119A (en) * | 2021-07-26 | 2021-12-03 | 上海闻泰信息技术有限公司 | Call stack backtracking method and device of embedded system and computer equipment |
| CN113742237A (en) * | 2021-09-13 | 2021-12-03 | 北京奕斯伟计算技术有限公司 | Program debugging method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110580226B (en) | Object code coverage rate testing method, system and medium for operating system level program | |
| EP1130518B1 (en) | Software analysis system having an apparatus for selectively collecting analysis data from a target system executing software instrumented with tag statements and method for use thereof | |
| US20210064512A1 (en) | Selective memory tracing of program execution | |
| Song et al. | The darpa cyber grand challenge: A competitor's perspective | |
| US8667255B2 (en) | Measuring runtime coverage of architectural events of a microprocessor | |
| CN102346235A (en) | Automatic test system and method for hardware device function | |
| RU2010114709A (en) | METHOD FOR AUTOMATIC GENERATION SCENARIO FOR CHECKING THE CORRECTNESS OF THE FUNCTIONAL SOFTWARE OF THE SYSTEM INSTALLED ON THE BOARD OF THE AIRCRAFT AND THE DEVICE FOR APPLICATION OF THE METHOD | |
| CN112084113A (en) | Configurable automatic test method and system based on embedded simulation verification software | |
| US11693760B2 (en) | System and methods for live debugging of transformed binaries | |
| WO2015079291A1 (en) | Code injection for conditional breakpoints | |
| CN111813672B (en) | Non-invasive coverage rate statistical method for various processor architectures | |
| CN108090352B (en) | Detection system and detection method | |
| US8972784B2 (en) | Method and device for testing a system comprising at least a plurality of software units that can be executed simultaneously | |
| EP3991075A1 (en) | Automatic correctness and performance measurement of binary transformation systems | |
| US7243059B2 (en) | Simulation of hardware based on smart buffer objects | |
| KR20140088963A (en) | System and method for testing runtime error | |
| CN111931191A (en) | Dynamic detection method and system for binary software stack overflow leakage hole of Linux platform | |
| CN114238098A (en) | Embedded software stack use condition dynamic analysis method and system based on data breakpoint | |
| CN111597115A (en) | Automatic closed-loop test system and test method for embedded operating system | |
| US11720474B2 (en) | System and methods for post mortem debugging of transformed binaries | |
| CN110096888B (en) | Method and system for accelerating verification and analyzing SMM potential safety hazard | |
| US20060064681A1 (en) | Method and system for verifying makefile accuracy | |
| CN114238096A (en) | Embedded software stack use condition dynamic analysis method and system based on single step exception | |
| CN110647467B (en) | Target code coverage rate testing method, system and medium based on single step exception | |
| CN111338761A (en) | 51 single-chip microcomputer virtual interrupt controller and implementation 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 |