Cross address space thread control in a multithreaded environment

• US 5,632,032 A
• Filed: 02/07/1994
• Issued: 05/20/1997
• Est. Priority Date: 02/07/1994
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Franks, Jon K., Walkowiak, Steven, Ault, Donald F., Bender, Ernest S.
• Primary Examiner(s): Kriess, Kevin A.
• Assistant Examiner(s): Toplu, Lucien
• Application Number:
  US08/192,929
• Time in Patent Office: 1,198 Days
• Field of Search: 371/19, 395/650, 395/670
• US Class Current: 718/100
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

A method of controlling the execution of the threads of a first application such as a user application from a second application such as a debugger application running in a different address space. After initializing trace mode for the user application, the debugger waits for an event to occur on one of the threads of the user application. Upon the occurrence of an event on one of the user application threads, an event handler obtains control of the thread execution. The event handler suspends execution of the remaining threads in the application, posts the debugger and then suspends its own execution. When the debugger application has completed its debugging operations, it posts the event handler, which resumes execution of the suspended threads and returns control to the thread on which the event occurred. If a subsequent event occurs on one thread while a previous event on another thread is being processed, the event handler for the subsequent event places it in a deferred event queue for deferred processing. Events consisting of breakpoints are redriven rather than being placed on the deferred queue. The debugger application may hold selected threads in a suspended state following resumption of the remaining threads by setting hold flags associated with those threads.

Claims

1. In a computer system having an application comprising a plurality of threads executing concurrently in a common address space, a method of handling the occurrence of a new event on a first one of said threads while a previous event on a second one of said threads is currently being processed, comprising the steps of:

(a) defining a flag indicating whether a previous event on one of said threads is currently being processed;

(b) defining a deferred event queue containing an entry for each event that cannot be processed immediately, said entry identifying the thread on which a deferred event occurred; and

(c) having said first one of said threads, in response to the occurrence of a new event on said thread;

(1) test said flag to determine whether a previous event is currently being processed;

(2) if said flag indicates that a previous event is not being processed, set said flag and process the new event; and

(3) if said flag indicates that a previous event is being processed, add the new event to said queue and suspend its own execution without processing said new event.

2. The method of claim 1 wherein the step of processing the new event includes the step of suspending the execution of each remaining thread of said application.

3. The method of claim 1 wherein said first one of said threads, upon completion of processing of said new event, performs the further steps of:

testing said deferred event queue to determine whether there is any deferred event requiring processing;

if there is no event in said deferred event queue, resuming normal execution of said threads; and

if there is a deferred event in said deferred event queue, resuming execution of the thread on which the deferred event occurred to permit said thread to process the deferred event.

4. The method of claim 3 wherein the thread that has completed the processing of an event suspends its own execution upon resuming execution of the thread on which the deferred event occurred.

5. The method of claim 3 wherein the thread on which the deferred event occurred removes the deferred queue entry for said deferred event upon resuming execution.

6. The method of claim 1 wherein said events include breakpoints and wherein the execution of each of said threads is controlled by an instruction counter pointing to an instruction next to be executed, said step (c)(3) comprising the steps of:

if the new event is not a breakpoint, adding the new event to said queue and suspending execution of said first one of said threads;

if said new event is a breakpoint, altering the instruction counter of said first one of said threads to point to said breakpoint and suspending execution of said thread without adding said new event to said queue.