CN105138453B - A kind of program debugging method and device - Google Patents
A kind of program debugging method and device Download PDFInfo
- Publication number
- CN105138453B CN105138453B CN201510493325.2A CN201510493325A CN105138453B CN 105138453 B CN105138453 B CN 105138453B CN 201510493325 A CN201510493325 A CN 201510493325A CN 105138453 B CN105138453 B CN 105138453B
- Authority
- CN
- China
- Prior art keywords
- debugging
- memory address
- version programs
- program
- debug
- 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
Landscapes
- Debugging And Monitoring (AREA)
Abstract
A kind of program debugging method of the application offer and device, wherein method include：According to the debugging position in the Debugging message of the Debug version programs of load setting, it is converted into corresponding memory address, the Debug version programs are corresponding with Release version programs to be tested；Program debugging device debugging action message in memory address and corresponding Debugging message being sent to where Release version programs, so that program debugging device carries out the corresponding debugging processing of debugging action message at the memory address of Release version programs；The debugging handling result that program debugging device returns is received, which includes memory address and result information, and memory address is converted to the debugging position of Debug version programs, obtains the result information at debugging position.The application improves the fault location efficiency to Release versions.
Description
Technical field
This application involves computer technology, more particularly to a kind of program debugging method and device.
Background technology
In the compiling generation phase of program, can be retained in final program code needed for some debugging by parameter setting
The information such as symbol table, in order to according to these information debugging routines come the logic loophole in finder, including these are debugged
The program version of the information such as required symbol table is properly termed as debugging version i.e. Debug versions.And when practical release process, for
The consideration of code cubage and safety, the program version for being delivered to client are generally released version i.e. Release versions.Release
Version is consistent with the function of Debug versions, only eliminates the information such as symbol.For example, being delivered to the net in user hand at some
The program that network equipment (e.g., router, interchanger) includes is the program of Release versions.
But it might be possible that due in laboratory environment it is limited, cause some problems be happened at user scene
Release versions in, such as generating routine operation troubles.It, can at present when positioning the guilty culprit of Release version programs
By use it is a kind of in a manner of be to be run according to Release versions in the dump image files that generate analyze failure, but dump is literary
Part can not generate and (only occur when fatal problem occurs) every time, alternatively, when not having dump files by locating personnel's root
Where guessing solution problem according to experience and communication, these modes all so that location efficiency is relatively low the problem of to Release version programs, from
And difficulty also is caused to the fault restoration of the equipment (for example, above-mentioned router, interchanger) where the operation of Release versions, shadow
Equipment is rung to use.
Invention content
In view of this, a kind of program debugging method of the application offer and device, fixed to the failure of Release versions to improve
Position efficiency.
Specifically, the application is achieved by the following technical solution：
In a first aspect, a kind of program debugging method is provided, including：
According to the debugging position in the Debugging message of the Debug version programs of load setting, with being converted into corresponding memory
Location, the Debug version programs are corresponding with Release version programs to be tested；
Debugging action message in the memory address and the corresponding Debugging message is sent to the Release
Program debugging device where version program, so that described program debugging apparatus is described in the Release version programs
The corresponding debugging processing of the debugging action message is carried out at memory address；
The debugging handling result that described program debugging apparatus returns is received, the debugging handling result includes the memory
The memory address is converted to the debugging position of Debug version programs, obtains the debugging by location and result information
The result information at position.
Second aspect provides a kind of program debugging method, including：
The memory address and corresponding debugging action that program debugging device where receiving Debug version programs is sent
Information, the Debug version programs are corresponding with Release version programs to be tested；
At the memory address of the Release version programs, the corresponding debugging of the debugging action message is carried out
Processing；
Debugging handling result fed back into described program debugging apparatus, the debugging handling result includes the memory
Location and result information, so that described program debugging apparatus is converted to the memory address described in Debug version programs
Position is debugged, the result information at the debugging position is obtained.
The third aspect provides a kind of program debugging device, including：
Address conversion module, the debugging position in Debugging message for being arranged according to the Debug version programs of load, turns
Change corresponding memory address into, the Debug version programs are corresponding with Release version programs to be tested；
Information sending module is used for the debugging action message in the memory address and the corresponding Debugging message
The program debugging device being sent to where the Release version programs, so that described program debugging apparatus is described
The corresponding debugging processing of the debugging action message is carried out at the memory address of Release version programs；
Transformation result module, the debugging handling result for receiving the return of described program debugging apparatus, the debugging processing
As a result include the memory address and result information, the memory address is converted to the debugging of Debug version programs
Position obtains the result information at the debugging position.
Fourth aspect provides a kind of program debugging device, including：
Information receiving module, for receive memory address that the program debugging device where Debug version programs sends, with
And corresponding debugging action message, the Debug version programs are corresponding with Release version programs to be tested；
Processing module is debugged, at the memory address of the Release version programs, carrying out the debugging action letter
Cease corresponding debugging processing；
As a result feedback module feeds back to described program debugging apparatus, the debugging processing knot for that will debug handling result
Fruit includes the memory address and result information, so that described program debugging apparatus is converted to the memory address
The debugging position of Debug version programs obtains the result information at the debugging position.
Program debugging method and device provided by the present application, by will be converted into the debugging position of Debug version programs
Memory address is sent to the program debugging device where Release version programs, can make according to memory address to Release
Version program carries out the debugging of source code grade, to improve the fault location efficiency to Release versions.
Description of the drawings
Fig. 1 is a kind of application scenarios of program debugging method shown in one exemplary embodiment of the application；
Fig. 2 is a kind of flow chart of program debugging method shown in one exemplary embodiment of the application；
Fig. 3 is the flow chart of another program debugging method shown in one exemplary embodiment of the application；
Fig. 4 is the flow chart of another program debugging method shown in one exemplary embodiment of the application；
Fig. 5 is a kind of structure chart of program debugging device shown in one exemplary embodiment of the application；
Fig. 6 is the structure chart of another program debugging device shown in one exemplary embodiment of the application.
Specific implementation mode
Example embodiments are described in detail here, and the example is illustrated in the accompanying drawings.Following description is related to
When attached drawing, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements.Following exemplary embodiment
Described in embodiment do not represent all embodiments consistent with the application.On the contrary, they be only with it is such as appended
The example of consistent device and method of some aspects be described in detail in claims, the application.
The program debugging method of the embodiment of the present application can be applied to the fault location to announced Release versions,
Such as it can be used for detecting the problem of Release version programs in router.
Fig. 1 illustrates the application scenarios of the program debugging method, as shown in Figure 1, equipped with to be tested in device A
Release version programs, tester can debug Release version programs by equipment B, with finder failure
Place.Certainly, it is same equipment to be also not excluded for device A and equipment B.
In order to debug Release version programs, tester can also prepare the following two kinds tool：
One of tool is Debug version programs corresponding with Release version programs to be tested：
For example, if Debug version programs and the compiling of Release version programs it is used source code it is identical, and compilation process
In, in addition to whether other than the parameter difference of the debugging information needed such as stet table, other parameters are consistent, then can be claimed
The program of both versions corresponds to.Also, Release versions are consistent with the function of Debug versions, only compare Debug versions
The debugging information needed such as symbol table is lacked.The Debug version programs corresponding with Release version programs to be tested can be with
The sides equipment B are located at, so that tester uses in debugging.
Another tool is program debugging system：
For example, as shown in Figure 1, the system may include：It is arranged in the program debugging tool client of equipment B, Yi Jishe
Set the program debugging tool server-side in device A.I.e. program debugging tool client can be arranged in this side of tester, add
Carry Debug version programs corresponding with Release version programs to be tested；And program debugging tool server-side can be arranged
Release version programs side to be tested, for loading Release versions, that is, the debugging target of the present embodiment.
The present embodiment is by taking the debugging system of gdb+gdbserver as an example, i.e., program debugging tool client for example can be
Gdb (GNU symbolic debugger, GNU symbolic debugger) loads Debug version programs, program debugging work by gdb
It can be gdbserver to have server-side for example, for loading Release version programs by gdbserver.In specific implementation
Other functionally similar program debugging tools can be used.
It, can be by the communication between gdb and gdbserver, to realize the present embodiment after preparing above two tool
Program debugging method.Wherein, it can be communicated by IP address and port numbers between gdb and gdbserver, for example,
After gdbserver is run at device A end, local particular port is monitored, the gdbserver in the gdb and device A of equipment B is supervised
The port listened establishes the link.
It by taking the debugging system of gdb+gdbserver as an example, will be described in detail how to combine Debug version programs pair as follows
Release version programs carry out the debugging of source code grade, and the debugging of the source code grade can be by Release version programs and Debug
The source code of version program establishes association, to search the source code for the failure problems for leading to Release version programs as soon as possible
Place.
Fig. 2 illustrates the flow of the program debugging method of the application, which is the program debugging tool client with equipment B
For holding gdb to execute, as shown in Fig. 2, may include：
201, it according to the debugging position in the Debugging message of the Debug version programs of load setting, is converted into corresponding
Address is deposited, the Debug version programs are corresponding with Release version programs to be tested；
For example, in actual implementation, can be determined by version number corresponding Debug version programs with it is to be tested
Release version programs.If the Debug version programs source code used with the compiling of Release version programs is identical and compiled
Cheng Zhong then can be in addition to whether other than the parameter difference of the debugging information needed such as stet table, other parameters are consistent
The program of both versions is claimed to correspond to.For this corresponding Debug version programs and Release version programs, can use
Identical version number.
202, the debugging action message in memory address and corresponding Debugging message is sent to Release version programs
The program debugging device at place, so that it is dynamic to carry out the debugging at the memory address of the Release version programs
Make the corresponding debugging processing of information；
203, the debugging handling result that described program debugging apparatus returns is received, the debugging handling result includes in described
Address and result information are deposited, the memory address is converted to the debugging position of Debug version programs, is obtained described
Debug the result information at position.
Fig. 3 illustrates the flow of the program debugging method of the application, which is the program debugging device with device A
For gdbserver is executed, as shown in figure 3, may include：
301, the memory address and corresponding debugging that the program debugging device where receiving Debug version programs is sent
Action message, Debug version programs are corresponding with Release version programs to be tested；
302, at the memory address of Release version programs, the corresponding debugging processing of debugging action message is carried out；
303, debugging handling result is fed back into described program debugging apparatus, debugging handling result includes the memory
Location and result information obtain so that memory address is converted to the debugging position of Debug version programs by program debugging device
The result information at debugging position.
In conjunction with shown in Fig. 2 and Fig. 3, in step 201, Debugging message can be arranged by the gdb of equipment B in tester,
The Debugging message may include：Debug position and debugging action message.
It therefore can be set in source code for example, Debug version programs are the source code file provided with Debugging message
Set the Debugging message such as breakpoint.In the present example, in the Debugging message of setting, debugging position is breakpoint setup position (e.g., in source
The 16th row of code file abc.c) and action message is debugged, which can be that the action of " setting breakpoint " refer to
Show, i.e., breakpoint is arranged in debugging position, which indicates, will suspend when program runs to 16 row, to facilitate tester
Check the operation results such as relevant variable value.
In another example when being debugged, in addition to above-mentioned setting breakpoint, the operation of some variables in program can also be obtained
Whether end value is checked, correct to detect operation result.In the present example, in the Debugging message of setting, debugging position can
Think and wants the corresponding variable position of the target variable of value (e.g., the 16th of source code file abc.c the in Debug version programs
Variable x) in row and debugging action message, the debugging action message can be " the operation result value for taking variable x ", the variable
X is properly termed as target variable, and debugging action obtains the value of target variable.
In step 201, gdb can carry out address conversion according to the Debugging message of above-mentioned setting, mainly believe debugging
Debugging position in breath is converted to corresponding memory address.For example, in the above example, breakpoint setup position (e.g., can be existed
The 16th row of source code file abc.c) it is converted into corresponding memory address, such as 0x123456；In another example can also be by the 16th
Variable x in row is also converted into corresponding memory address, i.e. the value of variable x is located in some corresponding memory address.
In step 202 and step 301, gdb can be by the memory address being converted in 201 and corresponding debugging
Action message is sent to gdbserver, and is that the protocol format that can be parsed with gdbserver is transmitted into row information；Equally,
When gdbserver transmits information to gdb, the protocol format that can be also parsed with gdb, so that program debugging device both sides' energy
The understanding enough communicated.
It can see by above-mentioned, the Release version programs of the gdbserver loads of device A itself are to be unable to corresponding source
Code file, for example, if gdb notices gdbserver installs breakpoint in the 16th line position of Release version programs, that
Release version programs will be unable to execute, because it not can know that the position of the source code point of interruption, other breakpoint informations are same
Reason does not know that x in source code corresponds to the position of Release itself if notice Release version programs obtain the value of variable x yet
It sets and cannot obtain；Based on this, the debugging position in Debugging message is converted to memory address by the gdb of the present embodiment,
The memory address that Release version programs and Debug version programs occupy at runtime is identical, therefore, passes through the memory
Address makes Release version programs determine the position of Debugging message.
Also, gdb will will also be notified to need to carry out in the memory address when informing the debugging corresponding memory address in position
Which kind of debugging processing, that is, debug action message；For example, " setting breakpoint " is carried out in breakpoint setup position, alternatively, in variable position
Obtain the corresponding value of target variable.
In step 302, the program debugging device gdbserver that A is arranged can be according to the tune received in step 301
Information is tried, in the position of the above-mentioned memory address of the correspondence of Release version programs, is carried out at the corresponding debugging of debugging action message
Reason.For example, being configured the action of breakpoint in breakpoint setup position；Alternatively, obtaining the variable in the corresponding memory address of variable x
The value of x.
In step 303, debugging handling result can also be fed back to the gdb of the sides equipment B by gdbserver, for equipment B
Tester check.The debugging handling result may include：Result information at memory address and the address.
For example, when Debugging message is when breakpoint is arranged in breakpoint setup position, then carrying out the result of debugging processing accordingly
Including " triggering breakpoint " and memory address, i.e. gdbserver notices gdb, which is realized in the position of " memory address ", " to be touched
The result of hair breakpoint ".In another example when Debugging message is when obtaining the value of variable x, then carrying out the knot of debugging processing accordingly
Fruit includes " value of variable x " i.e. operation result and " memory address ", and the memory address is the corresponding memories of variable x at this time
Address.
It should be noted that for the gdbserver of device A, as long as according in the Debugging message of gdb transmission
Memory address and debugging action message, carry out debugging processing, still, due to Release version programs not with source code pair
It answering, gdbserver can not know which kind of oss message corresponding at the memory address for carrying out debugging processing be, for example,
Gdbserver triggers breakpoint at the corresponding memory address 0x123456 of Release version programs, without can know that the address
It is the 16th row of sound code file that 0x123456 is corresponding；In another example gdbserver is corresponding one in Release version programs
Memory address obtains a value, but not can know that the value of the corresponding variable x for being sound code file of the value.Therefore,
In step 303, result information and corresponding memory address are returned to gdb by gdbserver.
And in step 203, the debugging handling result that gdb can be fed back according to gdbserver parses result letter therein
Which kind of position that corresponding memory address is source code is ceased, for example, when the gdbserver debugging handling results returned include " triggering
When breakpoint " (result information) and " 0x123456 " (memory address), gdb can carry out address conversion, by memory address
0x123456 is converted to the 16th rows of sound code file abc.c, to know that gdbserver is equivalent to Release version programs
The location triggered of the 16th row of source code breakpoint, i.e., the debugging result at debugging position initially set up in step 201
Information.
The program debugging method of above-mentioned example, by the way that Debugging message is arranged to Debug version programs in gdb debugging apparatus,
And the method converted using memory address, the memory address and tune for notifying Release version programs side to be tested to be debugged
Examination acts, and Release version programs can be made to execute the corresponding debugging processing of Debugging message of setting；Also, by by
Debugging result and memory address are fed back to gdb by the gdbserver where Release version programs, and gdb can also pass through address
The corresponding debugging result of Debugging message is known in conversion, to realize the debugging to Release version program source code grades, Neng Goujin
The problem of fast positioning Release versions corresponding source code position, improve the efficiency of fault location.
Such as next example, description carries out problem to Release version programs using the program debugging method of the application and determines
The process of position；Wherein, in this example, it is assumed that Release version programs mistake occur to the position of the 16th row of corresponding source code
Accidentally, and assume be variable x operation result mistake, then the flow example of Fig. 4 is fixed using the adjustment method of the present embodiment
Position goes out the step of problem place.As shown in figure 4, the flow is the communication process between gdb and gdbserver, may include：
501, the Debugging message of the Debug version programs setting of gdb acquisitions load, including breakpoint setup position and setting are broken
The action of point；
For example, the program debugging device gdb of equipment B installations, can load corresponding with Release version programs to be tested
Debug version programs.Also, Debugging message, including debugging position and in the position can be arranged in tester by gdb
The debugging action message at place.
Illustratively, in this step, it can be arranged and breakpoint is set in the position of the 16th row, that is, it is source code text to debug position
16 rows of part, debugging action are setting breakpoint.
502, breakpoint setup position is converted into memory address by gdb；
For example, gdb can be according to the Debug version programs of load by the 16th row this information conversions of sound code file abc.c
At a corresponding memory address, such as 0x123456.
503, gdb indicates the action of memory address and setting breakpoint, is transmitted to gdbserver；
For example, by above-mentioned memory address and breakpoint can be arranged by the protocol format that gdbserver can be parsed in gdb
Instruction is transmitted to gdbserver.
504, gdbserver triggers breakpoint at memory address to Release version programs；
For example, gdbserver receive 0x123456 and be arranged breakpoint information after, can be to Release versions
Program carries out the setting of breakpoint, and triggers breakpoint when the program runs to breakpoint location 0x123456.
505, gdbserver will debug handling result and feed back to gdb, including triggering breakpoint and memory address；
For example, in this step, gdbserver is equivalent to notice gdb, in the position pair of memory address 0x123456
Release version programs have carried out breakpoint trigger；Can by gdb it will be appreciated that protocol format send the information.
506, memory address is converted to the position of corresponding source code by gdb, obtains the result of debugging breakpoints；
For example, the address 0x123456 that gdbserver is returned in 505 can be carried out address conversion by gdb, the ground is obtained
Corresponding location is the 16th row of sound code file, the result information of comprehensive triggering breakpoint, that is, " Release version programs are in correspondence
The location triggered of 16 row of source code breakpoint " realizes the program debugging according to the Debugging message being arranged in step 501, triggering
Breakpoint.
After breakpoint trigger, tester can also check the operation result of some variable when program is suspended, for example, can
To check the operation result value of variable x that the 16th line position is set.It is possible to continue to execute 507, looking into for the value of variable x is carried out
It askes, this checks that variate-value also belongs to a kind of Debugging message.
507, gdb obtains the memory address for the target variable x to be inquired；
508, the action message of the memory address of variable x and acquisition variate-value is transmitted to gdbserver by gdb；
For example, in this step, being equivalent to gdb notice gdbserver in the position of the corresponding memory address, obtaining
The operation result of Release version programs.
509, gdbserver obtains value according to memory address；
For example, gdbserver can obtain the value stored at the address according to the memory address received in 508, but
It is that gdbserver and Release version programs are not aware that the corresponding source code position of the memory address is variable x.
510, value and corresponding memory address are fed back to gdb by gdbserver；
511, the memory address of value is carried out address conversion and obtains variable x by gdb, to be checked to obtaining tester
The value of variable x.
For example, it is assumed that the value of the variable x checked is 10, that is to say, that the operation of Release version programs in a device
When environment is run, the operation result of obtained variable x is 10；And assume that under normal circumstances, the result of variable x should be 8, that
The variable run-time error is assured that, then it is Release version programs the problem of institute that tester, which can navigate to this,
To carry out correction program.
In the above example, it is to be carried out to the method for program debugging by taking the checking of the setting of breakpoint and variable as an example
The principle of description, other debugging action is similar with the above process, repeats no more.It can also be obtained by above-mentioned example, it is this
The feedback of the transmission and debugging result of Debugging message is carried out by way of address conversion, can by Release version programs with
The Debug version programs of source code, which are established, to be corresponded to, and to realize the program debugging of source code grade, improves the debugging effect of Release versions
Rate.
Fig. 5 illustrates a kind of structure of program debugging device, which can be applied to program debugging tool client (example
Such as, gdb), the function of each unit and the realization process of effect specifically refer to the reality that step is corresponded in the above method in the device
Existing process, details are not described herein.As shown in figure 5, the debugging apparatus may include：Address conversion module 51, information sending module
52 and transformation result module 53；Wherein,
Address conversion module 51, the debugging position in Debugging message for being arranged according to the Debug version programs of load,
It is converted into corresponding memory address, the Debug version programs are corresponding with Release version programs to be tested；
Information sending module 52, for the debugging in the memory address and the corresponding Debugging message to be acted letter
Breath is sent to the program debugging device where the Release version programs, so that described program debugging apparatus is described
The corresponding debugging processing of the debugging action message is carried out at the memory address of Release version programs；
Transformation result module 53, the debugging handling result for receiving the return of described program debugging apparatus, at the debugging
It includes the memory address and result information to manage result, and the memory address is converted to the tune of Debug version programs
Position is tried, the result information at the debugging position is obtained.
For example, the debugging position, including：The breakpoint setup position of the Debug version programs；The debugging action letter
Breath, including：The action instruction of breakpoint is set.
In another example the debugging position, including：The corresponding change of the target variable of value is wanted in the Debug version programs
Measure position；Action message is debugged, including：Obtain the action instruction of target variable value.
Fig. 6 illustrates the structure of another program debugging device, which can be applied to program debugging tool server-side
(for example, gdbserver), the function of each unit and the realization process of effect specifically refer to corresponding in the above method in the device
The realization process of step, details are not described herein.As shown in fig. 6, the debugging apparatus may include：Information receiving module 61, debugging
Processing module 62 and result feedback module 63；Wherein,
Information receiving module 61, the memory address sent for the program debugging device where receiving Debug version programs,
And corresponding debugging action message, the Debug version programs are corresponding with Release version programs to be tested；
Processing module 62 is debugged, at the memory address of the Release version programs, carrying out the debugging action
The corresponding debugging processing of information；
As a result feedback module 63 feed back to described program debugging apparatus, the debugging processing for that will debug handling result
As a result include the memory address and result information, so that described program debugging apparatus is converted to the memory address
The debugging position of Debug version programs obtains the result information at the debugging position.
Further, debug processing module 62, specifically for will trigger breakpoint result or target variable value it is anti-
It is fed to described program debugging apparatus.
The foregoing is merely the preferred embodiments of the application, not limiting the application, all essences in the application
With within principle, any modification, equivalent substitution, improvement and etc. done should be included within the scope of the application protection god.
Claims (4)
1. a kind of program debugging method, which is characterized in that including：
According to the debugging position in the Debugging message of the Debug version programs of load setting, it is converted into corresponding memory address, institute
It is corresponding with Release version programs to be tested to state Debug version programs；
Debugging action message in the memory address and the corresponding Debugging message is sent to the Release versions
Program debugging device where program, so that the memory of the described program debugging apparatus in the Release version programs
The corresponding debugging processing of the debugging action message is carried out at address；
Receive described program debugging apparatus return debugging handling result, the debugging handling result include the memory address,
And result information, the memory address is converted to the debugging position of Debug version programs, obtains the debugging position
The result information at place；
The debugging position, including：The breakpoint setup position of the Debug version programs；The debugging action message, including：
The action instruction of breakpoint is set, or obtains the action instruction of target variable value.
2. a kind of program debugging method, which is characterized in that including：
The memory address and corresponding debugging action message that program debugging device where receiving Debug version programs is sent,
The Debug version programs are corresponding with Release version programs to be tested；
At the memory address of the Release version programs, the corresponding debugging processing of the debugging action message is carried out；
Debugging handling result is fed back into described program debugging apparatus, the debugging handling result include the memory address, with
And result information, so that the memory address is converted to the debugging position of Debug version programs by described program debugging apparatus,
Obtain the result information at the debugging position；
It is described that debugging handling result is fed back into described program debugging apparatus, including：The result for triggering breakpoint or target are become
The value of amount feeds back to described program debugging apparatus.
3. a kind of program debugging device, which is characterized in that including：
Address conversion module, the debugging position in Debugging message for being arranged according to the Debug version programs of load, is converted into
Corresponding memory address, the Debug version programs are corresponding with Release version programs to be tested；
Information sending module, for sending the debugging action message in the memory address and the corresponding Debugging message
To the program debugging device where the Release version programs, so that described program debugging apparatus is Release editions described
The corresponding debugging processing of the debugging action message is carried out at the memory address of this program；
Transformation result module, the debugging handling result for receiving the return of described program debugging apparatus, the debugging handling result
Including the memory address and result information, the memory address is converted to the debugging position of Debug version programs
It sets, obtains the result information at the debugging position；
The debugging position, including：The breakpoint setup position of the Debug version programs；The debugging action message, including：
The action instruction of breakpoint is set, or obtains the action instruction of target variable value.
4. a kind of program debugging device, which is characterized in that including：
Information receiving module, for receiving memory address that the program debugging device where Debug version programs is sent and right
The debugging action message answered, the Debug version programs are corresponding with Release version programs to be tested；
Processing module is debugged, at the memory address of the Release version programs, carrying out the debugging action message pair
The debugging processing answered；
As a result feedback module feeds back to described program debugging apparatus, the debugging handling result packet for that will debug handling result
The memory address and result information are included, so that the memory address is converted to Debug editions by described program debugging apparatus
The debugging position of this program obtains the result information at the debugging position；
The debugging processing module, specifically for the value of the result or target variable that trigger breakpoint is fed back to the journey
Sequence debugging apparatus.
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 CN105138453A (en) | 2015-12-09 |
| CN105138453B true 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) |
Families Citing this family (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 (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1286431A (en) * | 1999-11-30 | 2001-03-07 | 深圳市中兴通讯股份有限公司 | Embedded software aided debugging method |
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040054945A1 (en) * | 2002-09-17 | 2004-03-18 | Smith Gerald E. | Symbol support in embedded firmware images |
-
2015
- 2015-08-12 CN CN201510493325.2A patent/CN105138453B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1286431A (en) * | 1999-11-30 | 2001-03-07 | 深圳市中兴通讯股份有限公司 | Embedded software aided debugging method |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105138453A (en) | 2015-12-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8627146B2 (en) | Model-based testing of an application program under test | |
| CN106294102B (en) | Application program testing method, client, server and system | |
| CN102163173B (en) | Automated testing method for distributed information system interface | |
| US20070220492A1 (en) | Application verifier infrastructure and checks | |
| CN101795293A (en) | File download method, file download system, sending device and detecting device | |
| JP4745728B2 (en) | Debugging support program | |
| CN112737886A (en) | Tool testing method and system | |
| CN105138453B (en) | A kind of program debugging method and device | |
| Iyenghar et al. | Towards model-based test automation for embedded systems using UML and UTP | |
| CN109783284A (en) | Information acquisition method, system and server, computer readable storage medium | |
| CN109558318A (en) | A kind of code administration method and code storage distributed system | |
| WO2013121394A1 (en) | Remote debugging service | |
| Sasnauskas et al. | Integration testing of protocol implementations using symbolic distributed execution | |
| CN105227411B (en) | Method, network agent and the system of test interface | |
| CN111897789A (en) | Log generation method and device | |
| Bishop et al. | Project on diverse software—an experiment in software reliability | |
| CN109614337B (en) | Performance test system and test tool based on linux system | |
| Kim | Mobile applications software testing methodology | |
| CN101227346B (en) | Method and apparatus for failure monitoring in the course of communication equipment automatization testing | |
| CN113010187B (en) | Application installation method and device and electronic equipment | |
| Lima et al. | Towards decentralized conformance checking in model-based testing of distributed systems | |
| CN105260193A (en) | Self healing frame and healing method of large software | |
| CN115587046A (en) | Code exception processing method and device, storage medium and computer equipment | |
| Iyenghar et al. | An architecture for deploying model based testing in embedded systems | |
| CN104461629B (en) | PC terminals and its method for installing application program of mobile phone |
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 |