CN110347610B - Embedded code debugging system and method - Google Patents
Embedded code debugging system and method Download PDFInfo
- Publication number
- CN110347610B CN110347610B CN201910668008.8A CN201910668008A CN110347610B CN 110347610 B CN110347610 B CN 110347610B CN 201910668008 A CN201910668008 A CN 201910668008A CN 110347610 B CN110347610 B CN 110347610B
- Authority
- CN
- China
- Prior art keywords
- debugging
- code
- function
- information file
- real
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 238000012986 modification Methods 0.000 claims description 11
- 230000004048 modification Effects 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 10
- 230000003631 expected effect Effects 0.000 claims description 5
- 238000010276 construction Methods 0.000 claims description 3
- 210000001520 comb Anatomy 0.000 claims description 2
- 230000008676 import Effects 0.000 claims 1
- 238000004891 communication Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 241000282414 Homo sapiens Species 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
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/362—Software debugging
- G06F11/3624—Software debugging by performing operations on the source code, e.g. via a compiler
-
- 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/362—Software debugging
- G06F11/3628—Software debugging of optimised code
-
- 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/362—Software debugging
- G06F11/3636—Software debugging by tracing the execution of the program
-
- 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/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses an embedded application code debugging system and method, which reasonably evaluates each debugging result by fully utilizing each debugging information, so as to reduce the compiling and modifying times of codes in the debugging process and improve the debugging efficiency. The method mainly comprises a debugged host machine, an executable file, a real-time debugging information file frame, generation of a reference debugging information file and analysis of a debugging result, wherein the host machine is responsible for editing and compiling an embedded code; the embedded device is mainly responsible for executing executable files and real-time debugging information, and the host machine is connected with the embedded device through Ethernet or serial port protocol. The embedded application code debugging method mainly comprises the following steps: 1. writing a debugging code according to specific business logic; 2. generating reference debugging information; 3. generating real-time debugging information; 4. analyzing the debugging information and summarizing the debugging conclusion; 5. after the debugging is finished, the debugging records are tidied.
Description
Technical Field
The invention relates to the field of embedded application code debugging, in particular to an embedded application code debugging system and method.
Background
The embedded device has specific function and strong pertinence, and has software and hardware resources which are not as abundant as that of a PC, so that the code of the embedded application has the conditions of cross compiling and cross debugging, namely, the editing, compiling, linking and other processes of the application program are finished on the PC (also called Host), and finally the generated target code runs on the embedded device (also called target) which is very different from the PC. Because of the difference between compiling and running environments, each code debugging must be repeated by compiling, connecting, downloading and the like of the code, and the debugging information of each time cannot be fully utilized. Therefore, the embedded application program is inconvenient in the debugging process, and the code debugging efficiency is severely limited.
Meanwhile, in the activities of nature and human beings, various blurring phenomena exist, but since a blurring concept does not have a definite extension, whether an object accords with the blurring concept is difficult to determine, and thus uncertainty of a dividing result is caused. If a thing is evaluated for quality, the degree of quality or bad cannot be determined: for example, evaluating whether a code segment, a variable value, or both, meets the design's initial expectations or is somewhat different from the expected values has ambiguity and uncertainty. Clearly, conventional mathematical theory cannot accurately describe such binary logic problems.
In order to improve the accuracy of debugging description of the embedded application code, reduce the debugging times, improve the code debugging efficiency and reduce the debugging cost, the invention needs to provide an embedded application code debugging system and method.
Disclosure of Invention
The invention aims to provide an efficient embedded application code debugging system and method. According to the method, expert experience and fuzzy set theory are introduced into the embedded application code debugging process, the concept of parameter membership is introduced, the evaluation system of the debugging result is quantized, the debugging result is evaluated more objectively and accurately, the feedback information in the comprehensive debugging process can be accurately positioned to a specific step with a problem, the expert experience of related business is added, system parameters can be adjusted more accurately and objectively, and high-efficiency and accuracy of embedded application code debugging are achieved. The embedded application code debugging system mainly comprises embedded equipment for finally running an embedded code executable file; the PC with more abundant hardware resources is used for completing the processes of editing, compiling, linking and the like of the embedded application codes, generating a reference debugging information file and analyzing real-time debugging information.
The invention can fully utilize the debugging information of each time and provide accurate debugging position information. Meanwhile, the description and measurement of the accuracy of each step of debugging result are increased, the debugging accuracy is improved, and the number of times and time of preparation work in the debugging process are effectively reduced.
In order to achieve the above object, according to a first aspect of the present invention, a method for debugging an embedded application code is provided, which comprises the following steps in order:
step 1, generating debugging codes. According to business logic, writing embedded application codes for debugging: and step 2, generating a reference debugging information file. According to specific business logic, combing circle complexity in the embedded application code logic, introducing expert experience, constructing membership function families of key control parameters, function parameters and return values, and uniformly generating a reference debugging information file of the embedded application code:
and step 3, generating a real-time debugging information file. The compiler is called to compile codes of the embedded application to generate executable files, and meanwhile, entry parameters, function return values, line number information of the functions and the like during function call are collected in a code instrumentation mode to generate a real-time debugging information frame: step 4: downloading an executable file of the embedded application code into the embedded equipment in a network port or serial port communication mode, and running and debugging: step 5: and returning the real-time debugging information and backfilling the real-time debugging information file. Comparing the reference debugging information file, analyzing the debugging result of each step, determining the code problem position, adjusting the embedded application code, and debugging again. If the current debugging meets the expected result, ending the debugging.
The step 1 is mainly characterized in that an embedded application code is written according to specific business logic, and the corresponding physical meaning is recorded by lexical analysis and grammatical analysis to record the signs of variables, functions and constants of key control parameters: the step 2 is mainly characterized in that according to specific business logic and expert experience, an application code execution path is combed, key parameter names, function names and parameter names are collected, and a membership degree function family of related parameters based on trapezoidal fuzzy numbers is constructed:
the main feature of the step 3 is that the compiler is called to generate executable file information of the corresponding embedded equipment platform, and meanwhile, codes and processes for collecting corresponding real-time debugging information are added in a code instrumentation mode:
the main feature of the step 4 is that the executable file generated by compiling is downloaded to the embedded device, and the debugging operation is started, and the real-time debugging information is collected and stored:
the main characteristic of the step 5 is that the real-time debugging information is fed back to the host machine through the network port or the serial port in real time, and the real-time debugging information is counted and backfilled to the real-time debugging information file. Comparing the code execution paths in the real-time debugging information file and the reference debugging information file, comparing the key control parameters, the function return values and the running values of the function parameters, finding the membership function of the corresponding function, calculating the membership of the real-time debugging parameters, and adjusting the parameters with the membership less than 1 to enable the membership to be equal to or gradually approach to 1 in next debugging.
According to another aspect of the present invention, a system implementation scheme for embedded code debugging is also presented:
the code editing module is mainly characterized by an embedded code editing and compiling host machine:
the code execution path analysis module is mainly characterized in that a special experience system in the specific business industry is introduced, a debugger combs the code execution path, and the circle complexity of the code is calculated: the membership degree function family construction module is mainly characterized in that key parameters including control variable names, variable values, function names and function return values are carded according to specific business logic, and a membership degree function family based on trapezoidal fuzzy numbers is constructed according to expert experience: and generating the reference debugging information file. As schematically shown in fig. 4, the reference debug information is collated to generate a reference debug information file: the compiling processing module is mainly characterized in that an associated compiler is used for compiling embedded application codes, executable files operated by the embedded equipment are generated through linkage, and a frame of a real-time debugging information file is generated, wherein information such as entry parameters of function call, return values of functions, line numbers of the functions and the like is used as the frame of the real-time debugging information file, and collection of the information is realized through inserting codes in the compiling process. The function name, key control parameter name, line number, number of function parameters and return value are obtained when the embedded application code is subjected to lexical analysis and grammar analysis:
the debugging processing unit is mainly characterized in that an executable file is downloaded to the running debugging unit to run and debug. In the process, the running data of the function parameters and the return values are backfilled to a real-time debugging information file after running and debugging:
the analysis processing module is characterized by comparing and analyzing the real-time debugging information file with the reference debugging information file:
the first judging module is characterized in that the complexity of the code circle in the real-time debugging information file and the complexity of the code circle in the reference debugging information file are equal to each other: if the codes are consistent, the execution path of the codes and the calling sequence of the functions are described, and the next analysis is carried out:
if the line numbers are inconsistent, locating to an error position through the line numbers at the inconsistent position, making a debugging modification scheme, and continuing the next round of debugging:
the second judging module is characterized in that key control variables, function parameters, return value types and real-time values in the real-time debugging information file are imported into the reference debugging information file, and membership degrees are calculated according to the corresponding membership degree function: and selecting a membership function, and calculating the membership of the corresponding index parameter in the real-time debugging information. If the membership degree is 1 or is close to 1, the logical AND calculation of the parameter in the code is considered to meet the debugging requirement: if the membership is much greater or much less than 1, then the logical and computation of the parameter is considered to meet the non-debug requirements. If the function membership of all parameters meets the requirements, the debugging is considered to reach the expected effect, and the code debugging is passed. If the parameters do not meet the debugging requirements, determining the code position through the line number, and determining the modification scheme according to the deviation direction and the deviation size.
The invention is characterized in that
1. The embedded application code is debugged by comparing whether the dynamic real-time debugging information is consistent with the reference debugging information or not, errors and position information of the code to be debugged can be determined according to the comparison result, the storage appearing in the debugging can be accurately positioned, and the debugging modification direction is clear: 2. creation of the reference debug information file introduces expert experience and fuzzy set theory. Based on expert experience and specific business logic, the comb code runs logic: based on expert experience and fuzzy set theory, a membership function family of key parameter variables based on the trapezoidal fuzzy number is constructed. Calculating the membership degree of the real-time debugging operation value of the key parameter, quantitatively analyzing the debugging accuracy by the membership degree value, and qualitatively analyzing the debugging result.
Drawings
Figure l is a flow chart of an embedded application code debugging method:
FIG. 2 is a flow chart of an embedded application code debugging system:
fig. 3 is a flow of real-time debug information backfilling of real-time debug information files:
FIG. 4 is a template generated for a debug information file.
Detailed Description
The present invention will be further described with reference to the drawings in combination with specific embodiments for more clearly expressing the objects, technical solutions and advantages of the present invention.
The embedded application code debugging method is developed according to the flow chart of the embedded application code debugging method shown in the figure l. The embedded application codes written according to the business logic are compiled by a relevant compiler to generate executable files corresponding to the embedded platform, an instruction set containing all execution instructions is generated, and frame information of the real-time debugging information file is generated. The executable file is processed by the debugging processing unit and downloaded to the embedded application platform to start the debugging process. In the debugging process, each step of instruction execution, corresponding real-time debugging information is collected and output, and the real-time debugging information file is backfilled.
After each debugging is finished, the obtained real-time debugging information and the reference debugging information are processed, and all specific positions and methods which need to be adjusted or modified in the code can be determined. The entire code debugging process is repeatedly performed after modification, and at this time, the reference debugging information file can be cured as a debugging standard. When the code execution path in the dynamic information is consistent with that in the reference debugging file and the membership degree of the key control parameter is 1 or is close to 1, the debugging is considered to be finished: otherwise, the debugging proceeds.
The detailed implementation steps are as follows:
s, writing debugging codes:
and the Sl 1 debugger writes and instances the debugging codes conforming to the related programming specifications according to specific business logic and own professional literacy. In the writing process, note that symbol names of debugging elements such as key control parameters, code execution paths, function names and the like are collected, and physical meanings of the symbol names are recorded:
s2, generating reference debugging information;
s21, introducing experience of a special person in a specific business industry;
s22, calculating the complexity of the circle by a debugging personnel according to the execution path of the code:
s23, combing the parameters of the housekeeping, such as key control variable names, variable values, function names and function return values. The key control variables and the function return values are used for constructing a membership degree function family based on the trapezoidal fuzzy number according to the equal parameters and expert experience:
s24, according to the debug information file template shown in the figure 3, arranging and generating a reference debug information file:
s3, generating real-time debugging information:
s31, editing the embedded application code, and compiling the debugging code generated by the Sl by using a related compiler:
s32, generating an executable file for running the embedded equipment and generating a framework of a real-time debugging information file through linking. In the compiling process, the entry parameter of the function call, the return value of the function, the line number of the function and the like are used as the frame of the real-time debugging information file, and the collection of the information is realized through inserting codes in the compiling process. The function name, the key control parameter name, the line number, the number of the function parameters and the existence of the return value are obtained when the embedded application code is subjected to lexical analysis and grammar analysis, and at the moment, the operation data of the function parameters and the return value cannot be obtained yet;
s4, analyzing debugging information and summarizing a debugging conclusion:
s41, downloading the embedded application code executable file generated in the S2 to an embedded application platform thereof in a communication mode, and executing debugging operation. Backfilling implementation debugging information into a real-time debugging information file:
s42, returning the key control variables, the function parameters, the types of the return values and the real-time values and backfilling the real-time debugging information files through the execution of S41; s43, respectively comparing and analyzing code execution paths and circle complexity in codes in the real-time debugging information file and the reference debugging information file; if the execution paths are consistent, the execution paths of the codes and the calling sequence of the functions are described as being correct, and the process proceeds to step S44: if the line numbers are inconsistent, locating to an error position through the line numbers of the inconsistent positions, making a debugging modification scheme, and entering a step S5;
s44, importing the key control variable, the function parameter, the return value type and the real-time value in the real-time debugging information file into the reference debugging information file, and calculating the membership according to the corresponding membership function: and selecting a membership function, and calculating the membership of the corresponding index parameter in the real-time debugging information. If the membership degree is 1 or is close to 1, the logic and calculation of the parameter in the code are considered to meet the debugging requirement; if the membership degree is far more or far less than 1, the logical AND operation of the parameter is not considered to meet the debugging requirement. If the function membership of all parameters meets the requirements, the debugging is considered to reach the expected effect, and the code debugging is passed. If the parameters do not meet the debugging requirements, determining the code position through the line number, and determining a modification scheme according to the deviation direction and the size of the membership;
s5, after the debugging is finished, the debugging records are arranged:
and (3) sorting the debugging records, if the debugging records pass, considering that the code for the current debugging achieves the expected effect, and finishing the current debugging after the debugging passes: if the debugging record is not passed, entering S3 to continue the next debugging according to the debugging modification scheme.
The foregoing is merely exemplary embodiments of the present invention, and the objects, technical solutions and intentional effects of the present invention are further described, and thus the scope of the present invention is not limited thereto. All equivalent structures or equivalent flow changes which are convenient for the specification and the attached drawings of the invention or directly or indirectly operate in other professional technical fields are included in the protection scope of the invention.
Claims (2)
1. An embedded application code debugging method is characterized in that:
step one: generating debugging codes: writing an embedded application code for debugging according to the business logic;
step two: generating a reference debugging information file; according to specific business logic, introducing an expert experience system to generate a reference debugging information file of the embedded application code;
step three: generating a real-time debugging information file: calling a compiler to compile codes of the embedded application to generate an executable file, and collecting entry parameters, a function return value and line number information of the function in function calling in a code instrumentation mode to generate real-time debugging information;
step four: downloading an embedded application code execution file to the embedded equipment, and running and debugging;
step five: returning information in the real-time debugging information file, analyzing a debugging result according to the reference debugging information file, and adjusting the embedded application code;
in the second step, a reference debugging information file is generated, and an expert experience system in the industry is introduced: debugging personnel comb key control variable names, variable values, function names and function return values according to circle paths of codes, and the key control variable names, the variable values, the function names and the function return values are tidied to generate a reference debugging information file: the key control variables and the function return values construct membership degree function families based on the trapezoidal fuzzy numbers according to expert experience;
in the fifth step, the basis for judging whether the debugging is passed is derived from the comparison analysis result of the real-time debugging information file and the reference debugging information file: the first item is to compare and analyze the code circle path in the real-time debugging information file with the code circle path in the reference debugging information file: if the code is consistent, the execution path of the code and the calling sequence of the function are described as being correct, a second item of comparison analysis is entered, if the code is inconsistent, the debugging is considered to be failed, the error position is located through the line number of the inconsistent position, a debugging modification scheme is formulated, and the next round of debugging is continued; the second item is to import the key control variable, the function parameter, the return value type and the real-time value in the real-time debugging information file into the reference debugging information file, calculate the membership according to the corresponding membership function, select the membership function, and calculate the membership of the corresponding index parameter in the real-time debugging information; if the membership is 1 or is close to 1, the logic and calculation of the parameter in the code is considered to meet the debugging requirement, and if the membership is far more or far less than 1, the logic and calculation of the parameter is considered to meet the non-debugging requirement: if the function membership of all the parameters meets the requirements, the debugging is considered to reach the expected effect, and the code debugging is passed; if the parameters do not meet the debugging requirements, determining the code position through the line number, and determining the modification scheme according to the deviation direction and the deviation size.
2. An embedded application code debugging system, comprising: the system comprises a code editing module, a code execution path analysis module, a membership function family construction module, a reference debugging information file module, a compiling processing module, a debugging processing unit, an analysis processing module, a first judging module and a second judging module, wherein:
the code editing module is mainly characterized by an embedded code editing and compiling host;
the code execution path analysis module is mainly characterized in that a special experience system in the specific business industry is introduced, a debugger combs the code execution path, and the circle complexity of the code is calculated;
the membership degree function family construction module is mainly characterized in that key parameters including control variable names, variable values, function names and function return values are combed according to specific business logic, and a membership degree function family based on trapezoidal fuzzy numbers is constructed according to expert experience;
the reference debugging information file module is mainly characterized in that the reference debugging information is arranged according to a reference debugging information file template to generate a reference debugging information file;
the compiling processing module is mainly characterized in that a related compiler is used for compiling embedded application codes, executable files operated by the embedded equipment are generated through linkage, and a frame of a real-time debugging information file is generated, wherein entry parameters of function call, a function return value and line number information of the function are used as the frame of the real-time debugging information file, and the collection of the information is realized through inserting the code in the compiling process: the function name, the key control parameter name, the line number of the position, the number of the function parameters and whether the return value exists are obtained when the embedded application code is subjected to lexical analysis and grammar analysis;
the debugging processing unit is mainly characterized in that an executable file is downloaded to an operation debugging unit, and the operation debugging is performed: in the process, the running data of the function parameters and the return values are backfilled to a real-time debugging information file after running and debugging;
the analysis processing module is characterized by comparing and analyzing the real-time debugging information file with the reference debugging information file;
the first judging module is characterized in that the complexity of the code circle in the real-time debugging information file and the complexity of the code circle in the reference debugging information file are equal to each other: if the codes are consistent, the execution path of the codes and the calling sequence of the functions are described, and the next analysis is carried out; if the line numbers are inconsistent, locating to an error position through the line numbers at the inconsistent position, making a debugging modification scheme, and continuing the next round of debugging;
the second judging module is characterized in that key control variables, function parameters, return value types and real-time values in the real-time debugging information file are imported into the reference debugging information file, and membership degrees are calculated according to the corresponding membership degree function: selecting a membership function, calculating the membership of a corresponding index parameter in real-time debugging information, and if the membership is 1 or close to 1, considering that the logic and calculation of the parameter in the code accords with the debugging requirement:
if the membership degree is far more or far less than l, the logic and calculation of the parameter are considered to meet the non-debugging requirement, if the function membership degree of all the parameters meets the requirement, the debugging is considered to reach the expected effect, and the code debugging is performed by: if the parameters do not meet the debugging requirements, determining the code position through the line number, and determining the modification scheme according to the deviation direction and the deviation size.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910668008.8A CN110347610B (en) | 2019-07-23 | 2019-07-23 | Embedded code debugging system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910668008.8A CN110347610B (en) | 2019-07-23 | 2019-07-23 | Embedded code debugging system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110347610A CN110347610A (en) | 2019-10-18 |
| CN110347610B true CN110347610B (en) | 2023-10-27 |
Family
ID=68179941
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910668008.8A Active CN110347610B (en) | 2019-07-23 | 2019-07-23 | Embedded code debugging system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110347610B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626305A (en) * | 2021-06-23 | 2021-11-09 | 国网浙江省电力有限公司营销服务中心 | Debugging method and debugging system of non-invasive load identification algorithm |
| CN117311672A (en) * | 2022-06-24 | 2023-12-29 | 比亚迪股份有限公司 | Software model architecture, battery management system controller and vehicle |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5265254A (en) * | 1991-08-14 | 1993-11-23 | Hewlett-Packard Company | System of debugging software through use of code markers inserted into spaces in the source code during and after compilation |
| CN1585259A (en) * | 2004-06-10 | 2005-02-23 | 武汉理工大学 | DPS based intellectual high speed magnetic suspension control and analog power amplifying device |
| CN101976222A (en) * | 2010-11-03 | 2011-02-16 | 北京航空航天大学 | Framework-based real-time embedded software testability measuring method |
| CN103077112A (en) * | 2012-10-16 | 2013-05-01 | 中兴通讯股份有限公司 | Software debugging method and system |
| CN104765690A (en) * | 2015-04-22 | 2015-07-08 | 哈尔滨工业大学 | Embedded software test data generating method based on fuzzy-genetic algorithm |
-
2019
- 2019-07-23 CN CN201910668008.8A patent/CN110347610B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5265254A (en) * | 1991-08-14 | 1993-11-23 | Hewlett-Packard Company | System of debugging software through use of code markers inserted into spaces in the source code during and after compilation |
| CN1585259A (en) * | 2004-06-10 | 2005-02-23 | 武汉理工大学 | DPS based intellectual high speed magnetic suspension control and analog power amplifying device |
| CN101976222A (en) * | 2010-11-03 | 2011-02-16 | 北京航空航天大学 | Framework-based real-time embedded software testability measuring method |
| CN103077112A (en) * | 2012-10-16 | 2013-05-01 | 中兴通讯股份有限公司 | Software debugging method and system |
| CN104765690A (en) * | 2015-04-22 | 2015-07-08 | 哈尔滨工业大学 | Embedded software test data generating method based on fuzzy-genetic algorithm |
Non-Patent Citations (1)
| Title |
|---|
| 钟卫 ; 赵晓群 ; .基于Linux平台的DSP编程性能优化.燕山大学学报.2016,(05),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110347610A (en) | 2019-10-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Phipps | Comparing observed bug and productivity rates for Java and C++ | |
| Vokolos et al. | Pythia: A regression test selection tool based on textual differencing | |
| CN107368408A (en) | A kind of software fault towards interface injects automated testing method | |
| Gyimóthy et al. | Empirical validation of object-oriented metrics on open source software for fault prediction | |
| Korel | PELAS-program error-locating assistant system | |
| Swain et al. | Test Case Generation Based on State and Activity Models. | |
| Rountev et al. | Coverage criteria for testing of object interactions in sequence diagrams | |
| CN110347610B (en) | Embedded code debugging system and method | |
| Liu et al. | Automatic test case and test oracle generation based on functional scenarios in formal specifications for conformance testing | |
| CN108763064B (en) | Code test generation method and device based on black box function and machine learning | |
| Said et al. | On state machine mining from embedded control software | |
| Lorenzoli et al. | Inferring state-based behavior models | |
| Gómez et al. | Automatic time-bound analysis for a higher-order language | |
| Liu et al. | Software architectural model discovery from execution data | |
| Dwyer et al. | A compact petri net representation and its implications for analysis | |
| Fitzpatrick | Applying the ABC metric to C, C++, and Java | |
| CN107391124B (en) | Conditional slicing method based on golden section search and software execution track | |
| Merchant et al. | Tool for performance tuning and regression analyses of HPC systems and applications | |
| Shepperd | Products, processes and metrics | |
| CN113836023A (en) | Compiler security testing method based on system structure cross check | |
| Poulding et al. | Automated random testing in multiple dispatch languages | |
| Etemadi et al. | Augmenting Diffs With Runtime Information | |
| Rocha et al. | Test Case Generation by EFSM Extracted from UML Sequence Diagrams. | |
| Štolfa et al. | Methodology for estimating working time effort of the software project | |
| Godboley et al. | Dy-COPECA: A Dynamic Version of MC/DC Analyzer for C Program. |
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 |