Software Development With Information Describing Preceding Execution Of A Debuggable Program

• US 20130031534A1
• Filed: 07/27/2011
• Published: 01/31/2013
• Est. Priority Date: 07/27/2011
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bates, Cary L.
• Application Number:
  US13/191,546
• Publication Number:
  US 20130031534A1
• Time in Patent Office: Days
• US Class Current: 717/129
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

Software development with information describing preceding execution of a debuggable program includes receiving, by a debugger from a compiler, a copy of a debuggable program, the debuggable program including one or more phantom breakpoints not encountered during a previous execution of the debuggable program, each phantom breakpoint inserted at a separate line of source code, phantom breakpoints encountered in a previous execution of the debuggable program being removed during the previous execution and not included in the copy of the debuggable program; executing, by the debugger, the copy of the debuggable program; upon each encounter of a breakpoint, determining, by the debugger, whether the encountered breakpoint is a phantom breakpoint; and if the encountered breakpoint is a phantom breakpoint, issuing, by the debugger, a warning indicating a point of straying execution.

Claims

1. A method of software development with information describing preceding execution of a debuggable program, the method comprising:

receiving, by a debugger from a compiler, a copy of a debuggable program, the debuggable program comprising one or more phantom breakpoints not encountered during a previous execution of the debuggable program, each phantom breakpoint inserted at a separate line of source code, wherein phantom breakpoints encountered in a previous execution of the debuggable program were removed during the previous execution and not included in the copy of the debuggable program;

executing, by the debugger, the copy of the debuggable program;

upon each encounter of a breakpoint, determining, by the debugger, whether the encountered breakpoint comprises a phantom breakpoint; and

if the encountered breakpoint is a phantom breakpoint, issuing, by the debugger, a warning indicating a point of straying execution.

2. The method of claim 1 further comprising:

inserting, by the debugger upon request from a user, a breakpoint at a location in the copy of the debuggable program'"'"'s source code including;

determining whether a phantom breakpoint is inserted at the location; and

if a phantom breakpoint is inserted at the location, updating a breakpoint type attribute in an entry in a breakpoint table to reflect a user-specified breakpoint rather than a phantom breakpoint.

3. The method of claim 1 wherein issuing a warning indicating a point of straying execution further comprises issuing the warning only upon the first encounter of a phantom breakpoint.

4. The method of claim 3 wherein issuing the warning only upon the first encounter of a phantom breakpoint further comprises removing, upon the first encounter of the phantom breakpoint, all phantom breakpoints from the debuggable program.

5. The method of claim 3 wherein issuing the warning only upon the first encounter of a phantom breakpoint further comprises:

for each encounter of a phantom breakpoint;

removing the encountered phantom breakpoint and immediately resuming execution without user interaction.

6. The method of claim 1 further comprising:

inserting, by the compiler while compiling source code into the debuggable program, a phantom breakpoint at one or more lines of source code;

including in the debuggable program, by the compiler, the breakpoint handling module and the exit handler;

executing the debuggable program including encountering one or more of the phantom breakpoints and removing, by the breakpoint handling module, each encountered phantom breakpoint;

creating, by the exit handler, upon exiting execution of the debuggable program, the copy of the debuggable program that includes only phantom breakpoints not encountered during execution; and

providing the copy of the debuggable program to the debugger.

7. An apparatus for software development with information describing preceding execution of a debuggable program, the apparatus comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of:

receiving, by a debugger from a compiler, a copy of a debuggable program, the debuggable program comprising one or more phantom breakpoints not encountered during a previous execution of the debuggable program, each phantom breakpoint inserted at a separate line of source code, wherein phantom breakpoints encountered in a previous execution of the debuggable program were removed during the previous execution and not included in the copy of the debuggable program;

executing, by the debugger, the copy of the debuggable program;

upon each encounter of a breakpoint, determining, by the debugger, whether the encountered breakpoint comprises a phantom breakpoint; and

if the encountered breakpoint is a phantom breakpoint, issuing, by the debugger, a warning indicating a point of straying execution.

8. A computer program product for software development with information describing preceding execution of a debuggable program, the computer program product disposed upon a computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:

receiving, by a debugger from a compiler, a copy of a debuggable program, the debuggable program comprising one or more phantom breakpoints not encountered during a previous execution of the debuggable program, each phantom breakpoint inserted at a separate line of source code, wherein phantom breakpoints encountered in a previous execution of the debuggable program were removed during the previous execution and not included in the copy of the debuggable program;

executing, by the debugger, the copy of the debuggable program;

upon each encounter of a breakpoint, determining, by the debugger, whether the encountered breakpoint comprises a phantom breakpoint; and

if the encountered breakpoint is a phantom breakpoint, issuing, by the debugger, a warning indicating a point of straying execution.

9. The computer program product of claim 8 wherein the computer readable medium comprises a storage medium.

10. The computer program product of claim 8 wherein the computer readable medium comprises a transmission medium.

11. A method of software development with information describing preceding execution of a debuggable program, the debuggable program comprising a breakpoint handling module, an exit handler, and one or more phantom breakpoints inserted at compile time by a compiler, each phantom breakpoint inserted at a separate line of source code of the debuggable program, the method comprising:

executing the debuggable program one or more times outside of debugger control, including;

encountering, in at least one execution, one or more of the phantom breakpoints, and for each execution;

removing, by the breakpoint handling module, each encountered phantom breakpoint, resuming execution, and updating the debuggable program, by the exit handler upon exiting execution, to include only phantom breakpoints not encountered during the execution; and

managing phantom breakpoints in the debuggable program.

12. The method of claim 11 wherein managing phantom breakpoints in the debuggable program further comprises:

after the one or more executions of the debuggable program, resetting, responsive to a user request, each phantom breakpoint of the debuggable program inserted at compile time by the compiler and removed during the one or more executions.

13. The method of claim 11 wherein:

executing the debuggable program one or more times further comprises;

executing a plurality of instances of the debuggable program;

updating each instance of the debuggable program, separately, to include only phantom breakpoints not encountered during the execution of that instance; and

managing phantom breakpoints in the debuggable program further comprises merging the plurality of instances of the debuggable program into a merged instance of the debuggable program, the merged instance including only phantom breakpoints not encountered during any execution of any instance of the debuggable program.

14. The method of claim 11 further comprising loading, by a debugger, the debuggable program, wherein managing phantom breakpoints in the debuggable program further comprises:

receiving, by the debugger from a user, a selection of a portion of the debuggable program'"'"'s source code to track execution; and

executing the debuggable program under debugger control, including removing only phantom breakpoints encountered within the selected portion of the debuggable program'"'"'s source code.

15. The method of claim 14 wherein receiving, by the debugger from a user, a selection of a portion of the debuggable program'"'"'s source code to track execution further comprises removing, responsive to receiving the selected portion, phantom breakpoints from all portions of source code other than the selected portion.

16. The method of claim 14 wherein removing only phantom breakpoints encountered within the selected portion of the debuggable program'"'"'s source code further comprises ignoring encounters of phantom breakpoints not within the selected portion.

17. The method of claim 11 further comprising loading, by a debugger, the debuggable program, wherein managing phantom breakpoints in the debuggable program further comprises:

receiving, by the debugger from a user, a request prohibiting updating the debuggable program to include only phantom breakpoints not encountered during execution under debugger control;

disabling, by the debugger, the exit handler of the debuggable program; and

exiting execution under debugger control without updating one or more phantom breakpoints in the debuggable program in accordance with the request.

18. The method of claim 17 wherein receiving the request prohibiting updating the debuggable program further comprises one of:

receiving a request prohibiting updating a user-selected portion of source code;

receiving a request prohibiting updating portions of the debuggable program associated with the user;

receiving a request prohibiting updating portions other than portions associated with the debuggable program associated with the user;

or

executing one of a plurality of predefined debug commands.

19. An apparatus for software development with information describing preceding execution of a debuggable program, the debuggable program comprising a breakpoint handling module, an exit handler, and one or more phantom breakpoints inserted at compile time by a compiler, each phantom breakpoint inserted at a separate line of source code of the debuggable program, the apparatus comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of:

executing the debuggable program one or more times outside of debugger control, including;

encountering, in at least one execution, one or more of the phantom breakpoints, and for each execution;

removing, by the breakpoint handling module, each encountered phantom breakpoint, resuming execution, and updating the debuggable program, by the exit handler upon exiting execution, to include only phantom breakpoints not encountered during the execution; and

managing phantom breakpoints in the debuggable program.

20. A computer program product for software development with information describing preceding execution of a debuggable program, the debuggable program comprising a breakpoint handling module, an exit handler, and one or more phantom breakpoints inserted at compile time by a compiler, each phantom breakpoint inserted at a separate line of source code of the debuggable program, the computer program product disposed upon a computer readable storage medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:

executing the debuggable program one or more times outside of debugger control, including;

encountering, in at least one execution, one or more of the phantom breakpoints, and for each execution;

removing, by the breakpoint handling module, each encountered phantom breakpoint, resuming execution, and updating the debuggable program, by the exit handler upon exiting execution, to include only phantom breakpoints not encountered during the execution; and

managing phantom breakpoints in the debuggable program.