CN105138453A - Program debugging method and apparatus - Google Patents
Program debugging method and apparatus Download PDFInfo
- Publication number
- CN105138453A CN105138453A CN201510493325.2A CN201510493325A CN105138453A CN 105138453 A CN105138453 A CN 105138453A CN 201510493325 A CN201510493325 A CN 201510493325A CN 105138453 A CN105138453 A CN 105138453A
- Authority
- CN
- China
- Prior art keywords
- debugging
- program
- debug
- memory address
- version program
- 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
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The present application provides a program debugging method and apparatus. The method comprises: converting a debug position in debug information set according to a loaded Debug version program to a corresponding memory address, wherein the Debug version program corresponds to a to-be-tested Release version program; sending the memory address and debug action information in the corresponding debug information to a program debug apparatus in which the Release version program is to enable that the program debug apparatus performs debug processing corresponding to the debug action information at a memory address of the Release version program; and receiving a debug processing result returned from the program debug apparatus, and converting the memory address to the debug position of the Debug version program to obtain result information in the debug position, wherein the result comprises the memory address and the result information. According to the present application, the program debugging method and apparatus improve the fault locating efficiency of the Release version.
Description
Technical field
The application relates to computer technology, particularly a kind of program debugging method and device.
Background technology
At the compiling generation phase of program, the information such as the symbol table needed for some debugging can be retained in final program code by optimum configurations, so that carry out the logic leak in finder according to these information debugged programs, the program version comprising these information such as symbol table needed for debugging can be called debug version and Debug version.And during actual release process, for code cubage and safe consideration, the program version being delivered to client is generally released version and Release version.Release version is consistent with the function of Debug version, just eliminates the information such as symbol.Such as, the program that the network equipment (e.g., router, switch) be delivered in user's hand at some comprises is the program of Release version.
But the situation that may occur is, because in laboratory, environment is limited, some problems are caused to occur in the Release version at user scene, such as generating routine operation troubles.At present when locating the guilty culprit of Release version program, a kind of mode that can adopt is the dump image file analysis of failure produced in running according to Release version, but dump file not can produce (only occurring when there is fatal problem) at every turn, or, rule of thumb solution problem place is guessed with communication by locating personnel when there is no dump file, these modes all make the positioning problems efficiency of Release version program lower, thus also the equipment at place is run (such as to Release version, above-mentioned router, switch) fault restoration cause difficulty, affect equipment use.
Summary of the invention
In view of this, the application provides a kind of program debugging method and device, to improve the localization of fault efficiency to Release version.
Particularly, the application is achieved by the following technical solution:
First aspect, provides a kind of program debugging method, comprising:
According to the debugging position in the Debugging message that the Debug version program loaded is arranged, convert corresponding memory address to, described Debug version program is corresponding with Release version program to be tested;
Debug action information in the described Debugging message of described memory address and correspondence is sent to the program debugging device at described Release version program place, carries out debugging process corresponding to described debug action information to make described program debugging device at the described memory address place of described Release version program;
Receive the debugging result that described program debugging device returns, described debugging result comprises described memory address and object information, described memory address is converted to the described debugging position of Debug version program, obtains the described object information of described debugging position.
Second aspect, provides a kind of program debugging method, comprising:
The debug action information of the memory address that the program debugging device receiving Debug version program place sends and correspondence, described Debug version program is corresponding with Release version program to be tested;
At the described memory address place of described Release version program, carry out the debugging process that described debug action information is corresponding;
Debugging result is fed back to described program debugging device, described debugging result comprises described memory address and object information, with the described debugging position making described program debugging device described memory address is converted to Debug version program, obtain the described object information of described debugging position.
The third aspect, provides a kind of program debugging device, comprising:
Address conversion module, for the debugging position in the Debugging message of the Debug version program setting according to loading, convert corresponding memory address to, described Debug version program is corresponding with Release version program to be tested;
Information sending module, for the debug action information in the described Debugging message of described memory address and correspondence being sent to the program debugging device at described Release version program place, carry out debugging process corresponding to described debug action information to make described program debugging device at the described memory address place of described Release version program;
Transformation result module, for receiving the debugging result that described program debugging device returns, described debugging result comprises described memory address and object information, described memory address is converted to the described debugging position of Debug version program, obtains the described object information of described debugging position.
Fourth aspect, provides a kind of program debugging device, comprising:
Information receiving module, the debug action information of the memory address that the program debugging device for receiving Debug version program place sends and correspondence, described Debug version program is corresponding with Release version program to be tested;
Debugging processing module, for the memory address place at described Release version program, carries out the debugging process that described debug action information is corresponding;
Result feedback module, for debugging result is fed back to described program debugging device, described debugging result comprises described memory address and object information, with the described debugging position making described program debugging device described memory address is converted to Debug version program, obtain the described object information of described debugging position.
The program debugging method that the application provides and device, by converting to the debugging position of Debug version program the program debugging device that memory address is sent to Release version program place to, the debugging according to memory address, Release version program being carried out to source code level can be made, thus improve the localization of fault efficiency to Release version.
Accompanying drawing explanation
Fig. 1 is the application scenarios of a kind of program debugging method shown in the application one exemplary embodiment;
Fig. 2 is the process flow diagram of a kind of program debugging method shown in the application one exemplary embodiment;
Fig. 3 is the process flow diagram of the another kind of program debugging method shown in the application one exemplary embodiment;
Fig. 4 is the process flow diagram of another program debugging method shown in the application one exemplary embodiment;
Fig. 5 is the structural drawing of a kind of program debugging device shown in the application one exemplary embodiment;
Fig. 6 is the structural drawing of the another kind of program debugging device shown in the application one exemplary embodiment.
Embodiment
Here will be described exemplary embodiment in detail, its sample table shows in the accompanying drawings.When description below relates to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawing represents same or analogous key element.Embodiment described in following exemplary embodiment does not represent all embodiments consistent with the application.On the contrary, they only with as in appended claims describe in detail, the example of apparatus and method that some aspects of the application are consistent.
The program debugging method of the embodiment of the present application, can be applied to the localization of fault to announced Release version, such as, may be used for the problem detection of the Release version program in routers.
Fig. 1 illustrates the application scenarios of this program debugging method, and as shown in Figure 1, Release version program to be tested is housed in device A, tester can be debugged Release version program by equipment B, with finder guilty culprit.Certainly, also remover apparatus A and equipment B are not same equipment.
In order to debug Release version program, tester can also prepare the following two kinds instrument:
One of them instrument is, the Debug version program corresponding with Release version program to be tested:
Such as, if it is identical that Debug version program and Release version program compile source code used, and in compilation process, except whether the debugging information needed such as stet table parameter difference except, other parameters are all consistent, then the program of these two kinds of versions can be claimed corresponding.Further, Release version is consistent with the function of Debug version, just compares Debug version and has lacked the debugging information needed such as symbol table.Should can being located at equipment B side by the Debug version program corresponding with Release version program to be tested, using when debugging for tester.
Another instrument is, program debug system:
Such as, as shown in Figure 1, this system can comprise: be arranged on the program debugging tool client of equipment B and be arranged on the program debugging tool service end of device A.Namely program debugging tool client can be arranged on this side of tester, loads the Debug version program corresponding with Release version program to be tested; And program debugging tool service end can be arranged on Release version program side to be tested, for loading Release version, the namely debug target of the present embodiment.
The present embodiment is for the debug system of gdb+gdbserver, namely program debugging tool client-side is as being gdb (GNUsymbolicdebugger, GNU symbolic debugger), Debug version program is loaded by gdb, program debugging tool service end can be such as gdbserver, for loading Release version program by gdbserver.Also other functionally similar program debugging tools can be used in concrete enforcement.
After the above-mentioned two kinds of instruments of preparation, by the communication between gdb and gdbserver, the program debugging method of the present embodiment can be realized.Wherein, can be communicated between gdb and gdbserver by IP address and port numbers, such as, gdbserver, after device A end runs, monitors local particular port, and the port that the gdbserver in the gdb of equipment B and device A monitors establishes the link.
As follows by for the debug system of gdb+gdbserver, describe the debugging how in conjunction with Debug version program, Release version program being carried out to source code level in detail, namely the source code of Release version program with Debug version program can be associated by the debugging of this source code level, thus search the source code place of the failure problems causing Release version program as soon as possible.
Fig. 2 illustrates the flow process of the program debugging method of the application, and this flow process performs for the program debugging tool client gdb of equipment B, as shown in Figure 2, can comprise:
201, according to the debugging position in the Debugging message of the Debug version program setting loaded, convert corresponding memory address to, described Debug version program is corresponding with Release version program to be tested;
Such as, in reality is implemented, corresponding Debug version program and Release version program to be tested can be determined by version number.If it is identical that Debug version program and Release version program compile source code used, and in compilation process, except whether the debugging information needed such as stet table parameter difference except, other parameters are all consistent, then the program of these two kinds of versions can be claimed corresponding.For Debug version program and the Release version program of this correspondence, identical version number can be used.
202, the debug action information in the Debugging message of memory address and correspondence is sent to the program debugging device at Release version program place, to make to carry out debugging process corresponding to described debug action information at the described memory address place of described Release version program;
203, the debugging result that described program debugging device returns is received, described debugging result comprises described memory address and object information, described memory address is converted to the described debugging position of Debug version program, obtains the described object information of described debugging position.
Fig. 3 illustrates the flow process of the program debugging method of the application, and this flow process performs for the program debugging device gdbserver of device A, as shown in Figure 3, can comprise:
The debug action information of the memory address that the program debugging device 301, receiving Debug version program place sends and correspondence, Debug version program is corresponding with Release version program to be tested;
302, at the memory address place of Release version program, the debugging process that debug action information is corresponding is carried out;
303, debugging result is fed back to described program debugging device, debugging result comprises described memory address and object information, with the debugging position making program debugging device memory address is converted to Debug version program, obtain the described object information debugging position.
Shown in composition graphs 2 and Fig. 3, in step 201, tester can arrange Debugging message by the gdb of equipment B, and this Debugging message can comprise: debugging position and debug action information.
Such as, namely Debug version program is provided with the source code file of Debugging message, therefore, can arrange the Debugging message such as breakpoint in source code.In the present example, in the Debugging message arranged, debugging position be breakpoint setup position (as, the 16th row at source code file abc.c) and debug action information, this debug action information can indicate for the action of " arranging breakpoint ", and namely arrange breakpoint in debugging position, this breakpoint represents, to suspend when program runs to the 16th row, check the operation results such as relevant variable value to facilitate tester.
Again such as, when debugging, except above-mentioned arranges breakpoint, the operation result value of some variablees can also check in acquisition program, whether correct to detect operation result.In the present example, in the Debugging message arranged, debugging position can be want the target variable of value corresponding in Debug version program variable position (as, variable x in the 16th row of source code file abc.c) and debug action information, this debug action information can be " getting the operation result value of variable x ", this variable x can be called target variable, and namely debug action obtains the value of target variable.
In step 201, gdb according to the Debugging message of above-mentioned setting, can carry out address conversion, mainly the debugging position in Debugging message is converted to corresponding memory address.Such as, in the above example, breakpoint setup position (e.g., the 16th row at source code file abc.c) can be converted to corresponding memory address, such as 0x123456; Again such as, the variable x in the 16th row also can also be converted to corresponding memory address, namely the value of variable x is arranged in the memory address of certain correspondence.
In step 202 and step 301, the debug action information of the memory address be converted in 201 and correspondence can be sent to gdbserver by gdb, and is that the protocol format can resolved with gdbserver carries out information transmission; Equally, when gdbserver is to gdb transmission information, also with the protocol format that gdb can resolve, the understanding communicated can be carried out to make program debugging device both sides.
Can be seen by above-mentioned, the Release version program itself that the gdbserver of device A loads can not corresponding source code file, such as, if gdb notifies that gdbserver arranges breakpoint at the 16th line position of Release version program, so Release version program cannot perform, because it can not know the position of this source code point of interruption, other breakpoint informations in like manner, if notice Release version program obtains the value of variable x, it is not known the position of the corresponding Release self of x in source code yet and can not obtain; Based on this, debugging position in Debugging message is converted to memory address by the gdb of the present embodiment, the memory address that Release version program and Debug version program operationally take is identical, therefore, is made the position of Release version program determination Debugging message by this memory address.
Further, gdb when informing debugging memory address corresponding to position, also will will notify to need to carry out which kind of debugging process, i.e. debug action information at this memory address; Such as, carry out " breakpoint is set " in breakpoint setup position, or, obtain value corresponding to target variable at variable position.
In step 302, the program debugging device gdbserver arranging A according to the Debugging message received in step 301, in the position of the above-mentioned memory address of the correspondence of Release version program, can carry out the debugging process that debug action information is corresponding.Such as, carry out in breakpoint setup position the action that breakpoint is set; Or, the value of this variable x is obtained at the memory address that variable x is corresponding.
In step 303, debugging result can also be fed back to the gdb of equipment B side by gdbserver, and the tester for equipment B checks.This debugging result can comprise: the object information at memory address and this address place.
Such as, when Debugging message is when arranging breakpoint in breakpoint setup position, the result of carrying out debugging process so accordingly comprises " triggering breakpoints " and memory address, and namely gdbserver notifies that gdb has achieved the result of " triggering breakpoints " in the position of " memory address ".Again such as, when Debugging message is when obtaining the value of variable x, the result of carrying out debugging process so accordingly comprises " value of variable x " i.e. operation result and " memory address ", and now this memory address is the memory address that variable x is corresponding.
It should be noted that, for the gdbserver of device A, as long as it is according to the memory address in the Debugging message of gdb transmission and debug action information, carry out debugging to process, but, because Release version program is not corresponding with source code, gdbserver cannot know carry out debug process memory address place corresponding be which kind of oss message, such as, gdbserver at memory address 0x123456 place triggering breakpoints corresponding to Release version program, and can not know this address 0x123456 corresponding be the 16th row of sound code file; Again such as, gdbserver obtains a value at the memory address that Release version program is corresponding, but can not know this value corresponding be the value of the variable x of sound code file.Therefore, in step 303, the memory address of object information and correspondence will be returned to gdb by gdbserver.
And in step 203, gdb can according to the debugging result of gdbserver feedback, the memory address that parsing object information is wherein corresponding is which kind of position of source code, such as, when the debugging result that gdbserver returns comprises " triggering breakpoints " (object information) and " 0x123456 " (memory address), gdb can carry out address conversion, memory address 0x123456 is converted to sound code file abc.c the 16th row, thus know that gdbserver is equivalent to the location triggered breakpoint at source code the 16th row to Release version program, namely the debug results information of the debugging position of initial setting is in step 201 obtained.
The program debugging method of above-mentioned example, by arranging Debugging message at gdb debugging apparatus to Debug version program, and the method using memory address to change, notify the memory address that Release version program side to be tested carries out debugging and debug action, the debugging process that the Debugging message that the execution of Release version program can be made to arrange is corresponding; And, by debug results and memory address being fed back to gdb by the gdbserver at Release version program place, gdb also can know by address conversion the debug results that Debugging message is corresponding, thus the debugging achieved Release version program source code level, the source code position that the problem of Release version is corresponding can be located as soon as possible, improve the efficiency of localization of fault.
As next example, the process using the program debugging method of the application Release version program to be carried out to positioning problems is described; Wherein, in this example embodiment, suppose that mistake has appearred in the position of Release version program to the 16th row of corresponding source code, and hypothesis is the operation result mistake of variable x, so the flow example of Fig. 4 uses the adjustment method of the present embodiment to orient the step at this problem place.As shown in Figure 4, this flow process is the communication process between gdb and gdbserver, can comprise:
501, gdb obtains the Debugging message of the Debug version program setting loaded, and comprises breakpoint setup position and the action arranging breakpoint;
Such as, the program debugging device gdb that equipment B is installed, can load the Debug version program corresponding with Release version program to be tested.Further, tester can arrange Debugging message by gdb, comprises debugging position and the debug action information in this position.
Exemplary, in this step, the position that can be arranged on the 16th row arranges breakpoint, and namely debug 16 row that position is sound code file, debug action is for arranging breakpoint.
502, gdb converts breakpoint setup position to memory address;
Such as, this information of sound code file abc.c the 16th row can be converted to a corresponding memory address by gdb according to the Debug version program loaded, as 0x123456.
503, gdb is by memory address and the action instruction arranging breakpoint, transfers to gdbserver;
Such as, the protocol format that can be able to be resolved by gdbserver of gdb is by above-mentioned memory address and arrange breakpoint instruction and transfer to gdbserver.
504, gdbserver is at memory address place, to Release version program triggering breakpoints;
Such as, gdbserver, after the information receiving 0x123456 and arrange breakpoint, can carry out the setting of breakpoint to Release version program, and when this program runs to breakpoint location 0x123456 triggering breakpoints.
505, debugging result is fed back to gdb by gdbserver, comprises triggering breakpoints and memory address;
Such as, in this step, gdbserver is equivalent to notify gdb, has carried out breakpoint trigger in the position of memory address 0x123456 to Release version program; The protocol format can be able to understood by gdb sends this information.
506, memory address is converted to the position of corresponding source code by gdb, obtains the result of debugging breakpoints;
Such as, the address 0x123456 that gdbserver in 505 can return by gdb carries out address conversion, obtain this address corresponding be sound code file the 16th row, the object information of comprehensive triggering breakpoints, that is exactly " Release version program is at the location triggered breakpoint of corresponding source code 16 row ", achieve the program debug according to the Debugging message arranged in step 501, trigger breakpoint.
After breakpoint trigger, tester can also check the operation result of certain variable when program halt, such as, can check the operation result value of the variable x of the 16th line position.So, can continue execution 507, carry out the inquiry of the value of variable x, this checks that variate-value also belongs to a kind of Debugging message.
507, gdb obtains the memory address of the target variable x that will inquire about;
508, gdb is by the memory address of variable x and the action message obtaining variate-value, transfers to gdbserver;
Such as, in this step, be equivalent to the position that gdb notifies the memory address of gdbserver described in correspondence, obtain the operation result of Release version program.
509, gdbserver obtains value according to memory address;
Such as, gdbserver can according to the memory address received in 508, obtain the value that this address place stores, but gdbserver and Release version program do not know that the source code position that this memory address is corresponding is variable x.
510, the memory address of value and correspondence is fed back to gdb by gdbserver;
511, the memory address of value is carried out address and is converted to variable x by gdb, thus obtains the value of the variable x that tester will check.
Such as, suppose that the value of the variable x checked is 10, that is, when Release version program running environment is in a device run, the operation result of the variable x obtained is 10; And hypothesis under normal circumstances, the result of variable x should be 8, so just can determine this variable run-time error, and so tester can navigate to the problem place that this is Release version program, thus carries out correction program.
In the above example, be checking for the setting of breakpoint and variable, be described the method for program debug, principle and the said process of other debug action are similar, repeat no more.Can also be obtained by above-mentioned example, this mode changed by address carries out the transmission of Debugging message and the feedback of debug results, can Release version program be set up corresponding with the Debug version program of source code, thus realize the program debug of source code level, improve the debugging efficiency of Release version.
Fig. 5 illustrates a kind of structure of program debugging device, this device can be applied to program debugging tool client (such as, gdb), in this device, the implementation procedure of the function and efficacy of unit specifically refers to the implementation procedure of corresponding step in said method, does not repeat them here.As shown in Figure 5, this debugging apparatus can comprise: address conversion module 51, information sending module 52 and transformation result module 53; Wherein,
Address conversion module 51, for the debugging position in the Debugging message of the Debug version program setting according to loading, convert corresponding memory address to, described Debug version program is corresponding with Release version program to be tested;
Information sending module 52, for the debug action information in the described Debugging message of described memory address and correspondence being sent to the program debugging device at described Release version program place, carry out debugging process corresponding to described debug action information to make described program debugging device at the described memory address place of described Release version program;
Transformation result module 53, for receiving the debugging result that described program debugging device returns, described debugging result comprises described memory address and object information, described memory address is converted to the described debugging position of Debug version program, obtains the described object information of described debugging position.
Such as, described debugging position, comprising: the breakpoint setup position of described Debug version program; Described debug action information, comprising: the action instruction arranging breakpoint.
Again such as, described debugging position, comprising: the variable position wanting the target variable of value corresponding in described Debug version program; Debug action information, comprising: the action instruction obtaining target variable value.
Fig. 6 illustrates the structure of another kind of program debugging device, this device can be applied to program debugging tool service end (such as, gdbserver), in this device, the implementation procedure of the function and efficacy of unit specifically refers to the implementation procedure of corresponding step in said method, does not repeat them here.As shown in Figure 6, this debugging apparatus can comprise: information receiving module 61, debugging processing module 62 and result feedback module 63; Wherein,
Information receiving module 61, the debug action information of the memory address that the program debugging device for receiving Debug version program place sends and correspondence, described Debug version program is corresponding with Release version program to be tested;
Debugging processing module 62, for the memory address place at described Release version program, carries out the debugging process that described debug action information is corresponding;
Result feedback module 63, for debugging result is fed back to described program debugging device, described debugging result comprises described memory address and object information, with the described debugging position making described program debugging device described memory address is converted to Debug version program, obtain the described object information of described debugging position.
Further, debugging processing module 62, specifically for feeding back to described program debugging device by the result of triggering breakpoints or the value of target variable.
The foregoing is only the preferred embodiment of the application, not in order to limit the application, within all spirit in the application and principle, any amendment made, equivalent replacements, improvement etc., all should be included within scope that the application protects.
Claims (10)
1. a program debugging method, is characterized in that, comprising:
According to the debugging position in the Debugging message that the Debug version program loaded is arranged, convert corresponding memory address to, described Debug version program is corresponding with Release version program to be tested;
Debug action information in the described Debugging message of described memory address and correspondence is sent to the program debugging device at described Release version program place, carries out debugging process corresponding to described debug action information to make described program debugging device at the described memory address place of described Release version program;
Receive the debugging result that described program debugging device returns, described debugging result comprises described memory address and object information, described memory address is converted to the described debugging position of Debug version program, obtains the described object information of described debugging position.
2. method according to claim 1, is characterized in that, described debugging position, comprising: the breakpoint setup position of described Debug version program;
Described debug action information, comprising: the action instruction arranging breakpoint.
3. method according to claim 1, is characterized in that, described debugging position, comprising: the variable position wanting the target variable of value corresponding in described Debug version program;
Described debug action information, comprising: the action instruction obtaining described target variable value.
4. a program debugging method, is characterized in that, comprising:
The debug action information of the memory address that the program debugging device receiving Debug version program place sends and correspondence, described Debug version program is corresponding with Release version program to be tested;
At the described memory address place of described Release version program, carry out the debugging process that described debug action information is corresponding;
Debugging result is fed back to described program debugging device, described debugging result comprises described memory address and object information, with the described debugging position making described program debugging device described memory address is converted to Debug version program, obtain the described object information of described debugging position.
5. method according to claim 4, is characterized in that, described debugging result is fed back to described program debugging device, comprising:
The result of triggering breakpoints or the value of target variable are fed back to described program debugging device.
6. a program debugging device, is characterized in that, comprising:
Address conversion module, for the debugging position in the Debugging message of the Debug version program setting according to loading, convert corresponding memory address to, described Debug version program is corresponding with Release version program to be tested;
Information sending module, for the debug action information in the described Debugging message of described memory address and correspondence being sent to the program debugging device at described Release version program place, carry out debugging process corresponding to described debug action information to make described program debugging device at the described memory address place of described Release version program;
Transformation result module, for receiving the debugging result that described program debugging device returns, described debugging result comprises described memory address and object information, described memory address is converted to the described debugging position of Debug version program, obtains the described object information of described debugging position.
7. device according to claim 6, is characterized in that, described debugging position, comprising: the breakpoint setup position of described Debug version program;
Described debug action information, comprising: the action instruction arranging breakpoint.
8. device according to claim 6, is characterized in that, described debugging position, comprising: the variable position wanting the target variable of value corresponding in described Debug version program;
Described debug action information, comprising: the action instruction obtaining described target variable value.
9. a program debugging device, is characterized in that, comprising:
Information receiving module, the debug action information of the memory address that the program debugging device for receiving Debug version program place sends and correspondence, described Debug version program is corresponding with Release version program to be tested;
Debugging processing module, for the memory address place at described Release version program, carries out the debugging process that described debug action information is corresponding;
Result feedback module, for debugging result is fed back to described program debugging device, described debugging result comprises described memory address and object information, with the described debugging position making described program debugging device described memory address is converted to Debug version program, obtain the described object information of described debugging position.
10. device according to claim 9, is characterized in that,
Described debugging processing module, specifically for feeding back to described program debugging device by the result of triggering breakpoints or the value of target variable.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510493325.2A CN105138453B (en) | 2015-08-12 | 2015-08-12 | A kind of program debugging method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510493325.2A CN105138453B (en) | 2015-08-12 | 2015-08-12 | A kind of program debugging method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105138453A true CN105138453A (en) | 2015-12-09 |
| CN105138453B CN105138453B (en) | 2018-08-14 |
Family
ID=54723807
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510493325.2A Active CN105138453B (en) | 2015-08-12 | 2015-08-12 | A kind of program debugging method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105138453B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110532178A (en) * | 2019-08-09 | 2019-12-03 | 四川虹美智能科技有限公司 | A kind of Android system library file collapse location positioning method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1286431A (en) * | 1999-11-30 | 2001-03-07 | 深圳市中兴通讯股份有限公司 | Embedded software aided debugging method |
| US20040054945A1 (en) * | 2002-09-17 | 2004-03-18 | Smith Gerald E. | Symbol support in embedded firmware images |
| CN101178684A (en) * | 2006-11-06 | 2008-05-14 | 中兴通讯股份有限公司 | Symbol locating method of embedded system |
| CN101309475A (en) * | 2007-05-18 | 2008-11-19 | 中兴通讯股份有限公司 | Method for integrating debugging version and publishing version of communication terminal |
| CN101340314A (en) * | 2008-08-11 | 2009-01-07 | 中兴通讯股份有限公司 | Real-time debugging positioning method of embedded system and apparatus thereof |
| CN102073489A (en) * | 2009-11-23 | 2011-05-25 | 新奥特（北京）视频技术有限公司 | Method and device for generating debug log |
| CN103077112A (en) * | 2012-10-16 | 2013-05-01 | 中兴通讯股份有限公司 | Software debugging method and system |
-
2015
- 2015-08-12 CN CN201510493325.2A patent/CN105138453B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1286431A (en) * | 1999-11-30 | 2001-03-07 | 深圳市中兴通讯股份有限公司 | Embedded software aided debugging method |
| US20040054945A1 (en) * | 2002-09-17 | 2004-03-18 | Smith Gerald E. | Symbol support in embedded firmware images |
| CN101178684A (en) * | 2006-11-06 | 2008-05-14 | 中兴通讯股份有限公司 | Symbol locating method of embedded system |
| CN101309475A (en) * | 2007-05-18 | 2008-11-19 | 中兴通讯股份有限公司 | Method for integrating debugging version and publishing version of communication terminal |
| CN101340314A (en) * | 2008-08-11 | 2009-01-07 | 中兴通讯股份有限公司 | Real-time debugging positioning method of embedded system and apparatus thereof |
| CN102073489A (en) * | 2009-11-23 | 2011-05-25 | 新奥特（北京）视频技术有限公司 | Method and device for generating debug log |
| CN103077112A (en) * | 2012-10-16 | 2013-05-01 | 中兴通讯股份有限公司 | Software debugging method and system |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110532178A (en) * | 2019-08-09 | 2019-12-03 | 四川虹美智能科技有限公司 | A kind of Android system library file collapse location positioning method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105138453B (en) | 2018-08-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109800159B (en) | Program debugging method, program debugging device, terminal device, and storage medium | |
| CN112256570B (en) | Remote debugging method, device, equipment and storage medium | |
| US20110197098A1 (en) | Method and apparatus for test coverage analysis | |
| CN103580943A (en) | Network software online testing method and system | |
| CN106851513B (en) | Method and system for testing electronic product | |
| CN101795293A (en) | File download method, file download system, sending device and detecting device | |
| JP4745728B2 (en) | Debugging support program | |
| CN1701305A (en) | Bi-directional probing of software | |
| US20070047448A1 (en) | Network equipment testing method and system | |
| CN105138453A (en) | Program debugging method and apparatus | |
| WO2020087956A1 (en) | Method, apparatus, device and system for capturing trace of nvme hard disc | |
| Dao et al. | Live debugging of distributed systems | |
| Sasnauskas et al. | Integration testing of protocol implementations using symbolic distributed execution | |
| Barbosa et al. | Verification and validation of (real time) COTS products using fault injection techniques | |
| CN103176903B (en) | The test method and equipment of MapReduce distributed system program | |
| CN104951297A (en) | Integrated development environment (IDE) operating in Web end | |
| CN106708488A (en) | Multi-application debugging system and method | |
| KR101648307B1 (en) | Log-based testing system and method for unit testing of Embedded software | |
| CN101227346B (en) | Method and apparatus for failure monitoring in the course of communication equipment automatization testing | |
| Kim | Mobile applications software testing methodology | |
| CN103257924B (en) | GDB agency adjustment method and device | |
| Dinh et al. | Scalable relative debugging | |
| CN107911264A (en) | Programmable route exchange device on-line debugging device and method | |
| Timperley et al. | 188 ROS bugs later: Where do we go from here | |
| David et al. | From source code to crash test-cases through software testing automation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |