Debugging techniques in a multithreaded environment

• US 6,848,097 B1
• Filed: 09/18/2002
• Issued: 01/25/2005
• Est. Priority Date: 11/13/1998
• Status: Expired due to Fees

• Current Assignee: CRAY Incorporated (Hewlett-Packard Enterprise Company)
• Original Assignee: CRAY Incorporated (Hewlett-Packard Enterprise Company)
• Inventors: Alverson, Gail A., Smith, Burton J., Kaplan, Laurence S., Niehaus, Mark L.
• Primary Examiner(s): ZHEN, WEI Y
• Application Number:
  US10/247,276
• Time in Patent Office: 860 Days
• Field of Search: 717124-135, 703 26- 27, 714/30, 712/244
• US Class Current: 717/124
• CPC Class Codes: G06F 11/362 Software debugging

Abstract

A system for debugging targets using various techniques, some of which are particularly useful in a multithread environment. These techniques include implementing breakpoints using out-of-line instruction emulation so that an instruction replaced with a breakpoint instruction does not need to be returned to its original location for single-step execution, executing a debugger nub for each target as part of the target task but using a nub task thread for the nub execution that is separate from the target task threads, providing immunity from breakpoints for specified threads such as the nub thread via specialized breakpoint handlers used by those threads, and virtualizing the debugger nub such that a shared root nub provides a uniform interface between the debugger and the target while specialized nubs provide differing functionality based on the type of target being debugged.

Claims

1. A computer-implemented method for debugging targets using debugger nubs, the method comprising:

executing a first debugger nub associated with a first target, the first debugger nub being of a first debugger nub type;

executing a second debugger nub associated with a second target, the second debugger nub being of a second debugger nub type that is distinct from the first debugger nub type;

when the first debugger nub receives a first instruction from a debugger to provide indicated functionality, providing the indicated functionality in a manner specific to the first debugger nub type; and

when the second debugger nub receives the first instruction from the debugger to provide the indicated functionality, providing the indicated functionality in a manner specific to the second debugger nub type that is distinct from the manner specific to the first debugger nub type.

2. The method of claim 1 including executing the first target using multiple software threads, and wherein the first debugger nub is executed using one of the threads.

3. The method of claim 1 wherein the first target is an executing application program, and wherein the first debugger nub type corresponds to executing application programs.

4. The method of claim 3 wherein the providing of the indicated functionality by the first debugger nub type includes interacting with the executing first target.

5. The method of claim 1 wherein the first target is an executing operating system, and wherein the first debugger nub type corresponds to executing operating systems.

6. The method of claim 5 wherein the providing of the indicated functionality by the first debugger nub type includes interacting with the executing first target.

7. The method of claim 1 wherein the first target has associated static dump state information, and wherein the first debugger nub type corresponds to static dump state information.

8. The method of claim 7 wherein the providing of the indicated functionality by the first debugger nub type includes retrieving information about the first target from the associated static dump state information.

9. The method of claim 1 wherein a type of a debugger nub is chosen based on a type of target with which the debugger nub will be associated.

10. The method of claim 1 wherein the first instruction received by the first and second debugger nubs is specified by the debugger in a uniform manner.

11. The method of claim 1 including:

when the first debugger nub receives a second instruction from the debugger to provide indicated functionality, providing the indicated functionality in a manner common to debugger nubs of multiple types; and

when the second debugger nub receives the second instruction from the debugger to provide the indicated functionality, providing the indicated functionality in the same manner as did the first debugger nub.

12. The method of claim 1 including:

when the first debugger nub receives a second instruction from the debugger to provide indicated functionality, providing the indicated functionality; and

when the second debugger nub receives the second instruction from the debugger to provide the indicated functionality, indicating to the debugger an inability to provide the indicated functionality.

13. The method of claim 1 wherein the indicated functionality provided by the first and second debugger nubs is to set a breakpoint in the target with which that debugger nub is associated.

14. The method of claim 1 wherein the indicated functionality provided by the first and second debugger nubs is to evaluate an expression using a current state of the target with which that debugger nub is associated.

15. The method of claim 1 wherein the types of the debugger nubs are distinct debugger nub classes that each inherit from a common root nub class.

16. The method of claim 15 wherein the distinct debugger nub classes correspond to types of target with which debugger nubs of those classes will be associated.

17. The method of claim 15 wherein the common root nub class provides a uniform interface to the debugger for communicating with debugger nubs of distinct debugger nub classes.

18. The method of claim 15 wherein the common root nub class provides a public implementation of debugger nub functionalities that are not performed in a manner specific to the types of debugger nubs, the debugger nubs of the distinct debugger nub classes inheriting the public implementation of those debugger nub functionalities.

19. The method of claim 15 wherein the common root nub class provides pure virtual function indications for debugger nub functionalities that must be performed in a manner specific to the types of debugger nubs, and wherein the distinct debugger nub classes each provide an implementation of those debugger nub functionalities.

20. The method of claim 15 wherein the common root nub class provides virtual function implementations of debugger nub functionalities that can be performed in a default manner or in a manner specific to the types of debugger nubs, wherein the virtual function implementations perform the debugger nub functionalities in a default manner, and wherein, for each of the virtual function implementations of a debugger nub functionality, some of the distinct debugger nub classes inherit and use that virtual function implementation and some of the distinct debugger nub classes each provide an implementation of that debugger nub functionality that replaces the virtual function implementation.

21. The method of claim 1 including executing the debugger.

22. The method of claim 1 wherein at least one of the first and second targets executes on a processor using multiple software threads, and wherein the processor has multiple hardware streams each able to execute at least one of the software threads.

23. The method of claim 22 wherein the processor has multiple protection domains that are each able to execute a program, and wherein at least one of the first and second targets executes in the protection domains.

24. A computer-readable medium whose contents cause a computing device to debug targets using debugger nubs, by performing steps comprising:

executing a first debugger nub associated with a first target, the first debugger nub being of a first debugger nub type,

executing a second debugger nub associated with a second target, the second debugger nub being of a second debugger nub type that is distinct from the first debugger nub type;

when the first debugger nub receives a first instruction from a debugger to provide indicated functionality, providing the indicated functionality in a manner specific to the first debugger nub type; and

when the second debugger nub receives the first instruction from the debugger to provide the indicated functionality, providing the indicated functionality in a manner specific to the second debugger nub type that is distinct from the manner specific to the first debugger nub type.

25. The computer-readable medium of claim 24 wherein the types of the debugger nubs are distinct debugger nub classes that each inherit from a common root nub class, and wherein the distinct debugger nub classes correspond to types of target with which debugger nubs of those classes will be associated.

26. A computing device for debugging targets using debugger nubs, comprising:

a debugger nub execution component that is capable of executing a first debugger nub associated with a first target, the first debugger nub being of a first debugger nub type, and of executing a second debugger nub associated with a second target, the second debugger nub being of a second debugger nub type that is distinct from the first debugger nub type;

the executing first debugger nub that receives a first instruction from a debugger to provide indicated functionality, and that provides the indicated functionality in a manner specific to the first debugger nub type; and

the executing second debugger nub that receives the first instruction from the debugger to provide the indicated functionality, and that provides the indicated functionality in a manner specific to the second debugger nub type that is distinct from the manner specific to the first debugger nub type.