US 8,752,022 B2Granted

Thread-specific event management in a non-stop debugging environment

AssigneeInternational Business Machines Corporation

InventorCary L. Bates

Life of this patent

Estimating the term…

Loading patent…

Abstract

A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee. In the non-stop debugging environment, encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of the other threads. Thread-specific events may managed in the non-stop debug environment by identifying, by the debugger for a thread of execution of the debuggee not currently executing, a thread-specific event associated with the thread; removing, by the debugger, the thread-specific event for all threads of the debuggee; and upon the thread resuming execution, replacing, by the debugger, the thread-specific event.

Claims12

Dependent claims

An apparatus for thread-specific event management in a non-stop debugging environment, the non-stop debugging environment comprising a debugger configured to debug a debuggee comprising a plurality of threads of execution, wherein encountering an event by one of the threads stop execution of only the one thread without concurrently stopping execution of the other threads, 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:

identifying, by the debugger for a thread of execution of the debuggee not currently executing, a thread-specific event associated with the thread, wherein the thread specific event comprises predefined operation code previously inserted into original operational code for the thread of execution;
tracking a number of encounters of the thread-specific breakpoint while the thread is not executing;
in response to determining that the number of encounters exceeds a predetermined threshold, removing, by the debugger, the thread-specific event for all threads of the debuggee while the thread of execution associated with the thread-specific event is not currently executing;
and
upon the thread resuming execution, replacing, by the debugger, the thread-specific event.

2 more elements

A computer program product for thread-specific event management in a non-stop debugging environment, the non-stop debugging environment comprising a debugger configured to debug a debuggee comprising a plurality of threads of execution, wherein encountering an event by one of the threads stop execution of only the one thread without concurrently stopping execution of the other threads, the computer program product disposed upon a non-transitory computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:

identifying, by the debugger for a thread of execution of the debuggee not currently executing, a thread-specific event associated with the thread, wherein the thread specific event comprises predefined operation code previously inserted into original operational code for the thread of execution;
tracking a number of encounters of the thread-specific event while the thread is not executing;
in response to determining that the number of encounters exceeds a predetermined threshold, removing, by the debugger, the thread-specific event for all threads of the debuggee while the thread of execution associated with the thread-specific event is not currently executing;
and
upon the thread resuming execution, replacing, by the debugger, the thread-specific event.

2 more elements

Dependencies are inferred from the claim text.