Method and system for remotely debugging a hung or crashed computing system

• US 8,069,371 B2
• Filed: 04/25/2008
• Issued: 11/29/2011
• Est. Priority Date: 04/26/2007
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Krishnamurthy, Vinay, Sengupta, Sabyasachi
• Primary Examiner(s): LE, DIEU MINH T
• Application Number:
  US12/110,180
• Publication Number:
  US 20080295077A1
• Time in Patent Office: 1,313 Days
• Field of Search: 714/37, 714/38, 714/39, 714/38.1, 714/38.12, 714/38.13, 714/38.14, 717/124, 717/126, 717/128
• US Class Current: 714/37
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0778 Dumping, i.e. gathering error/state information after a fault for later diagnosis
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence

Abstract

A method and system for debugging a computer upon a kernel hang and/or upon a software failure, the method comprising executing a debugger on a remote computer, connecting the hung or crashed computer to the remote computer with a communications link, and debugging the hung or crashed computer with the debugger without rebooting the system. The method may include deconfiguring any kernel driver of the computer attached to the communication card prior to connecting the remote debugger to the computer.

Claims

1. A method for debugging a hung or crashed computing system or panicked software, comprising:

executing a debugger on a remote computer;

connecting said computing system to said remote computer with a communications link comprising deconfiguring a kernel driver in said computing system that previously controlled a communications link interface card and substituting a kernel debugger driver for controlling said communications link interface card to connect said computing system to said remote computer; and

debugging said operating system or said panicked software of said computing system with said debugger.

2. A method as claimed in claim 1, including destroying the instance of said debugger used for said debugging after completing said debugging with said debugger.

3. A method as claimed in claim 1, including said operating system of said computer reclaiming a communications card of said computing system used for connecting to said remote computer.

4. The method of claim 1, wherein said debugger terminates one or more processes running on said computing system.

5. The method of claim 1, wherein said communications link comprises a Data Link Provider Interface (DLPI) and a communication server between the computing system and remote computer with the debugger.

6. A method for debugging a computing device, comprising:

deconfiguring a kernel driver in said computing system that previously controlled a communications link interface card and substituting a kernel debugger driver for controlling said communications link interface card;

with said kernel debugger driver operating said communications link interface card, establishing a communications link with a remote computer that is executing a debugger.

7. The method of claim 6, further comprising debugging an operating system or panicked software of said computing system with said debugger.

8. The method of claim 6, further comprising receiving a designated key sequence input by an administrator to an interrupt handler which initializes a debugger subsystem of the computing system that performs said deconfiguring of said kernel driver.

9. The method of claim 6, further comprising stopping everything except a single foreground processor of the computing system when the debugger has connected to the computing system.

10. The method of claim 6, wherein said communications link comprises a Data Link Provider Interface (DLPI) and a communication server between the computing system and remote computer with the debugger.

11. The method of claim 6, wherein said communications link with said remote computer comprises a UDP/IP stack.

12. A computing system, comprising:

an operating system;

a remote computing device;

a communications link for connecting said computing system and said remote computing device; and

a debugger accessible by said remote computing device and executable on said remote computing device;

wherein said remote computing device is operable to connect to said computing system with said communications link and to execute said debugger, said debugger being operable by a user to debug said operating system or panicked software following said operating system hanging or crashing or said software panicking; and

wherein said computing system is configured to deconfigure a kernel driver of said operating system in response to a hanging or crashing of said operating system and substitute a kernel debugger driver for controlling said communications link interface card prior to connecting to said remote computer.

13. A system as claimed in claim 12, wherein said remote computer is configured to destroy the instance of said debugger used to debug said operating system or said panicked software after said operating system or said panicked software has been debugged.

14. A system as claimed in claim 12, wherein said operating system is configured to reclaim a communications card of said computing system used for connecting to said remote computer.

15. A computing system configured to be debugged remotely and having an operating system, comprising:

a computer configured in response to said operating system hanging or crashing or in response to a panic of other software of said computing system to deconfigure a kernel driver of said computer, to connect to a remote computer provided with a remote debugger, and to accept debugging commands from said remote debugger for said operating system or said other software.

16. A system as claimed in claim 15, wherein said computer is configured to reclaim a communications card of said computer used for connecting to said remote computer.

17. The computing system of claim 15, wherein said connection with said remote computer comprises a Data Link Provider Interface (DLPI) and a communication server between the computing system and remote computer with the remote debugger.

18. The computing system of claim 15, said computer further configured to substitute a debugger kernel driver for said deconfigured kernel driver during communication with said remote computer.

19. The computing system of claim 15, wherein said connection with said remote computer comprises a UDP/IP stack.