Techniques for debugging code during runtime

Abstract

A technique for debugging code during runtime includes providing, from an outside process, a trigger to a daemon. In this case, the trigger is associated with a registered callback function. The trigger is then provided, from the daemon, to one or more designated tasks of a job. The registered callback function (that is associated with the trigger) is then executed by the one or more designated tasks. Execution results of the executed registered callback function are then returned (from the one or more designated tasks) to the daemon.

What is claimed is: 
     
       1. A method for debugging code during runtime, comprising:
 providing, from an outside process, a trigger to a daemon, wherein the trigger is associated with a registered callback function; 
 providing, from the daemon, the trigger to one or more designated tasks of a job; 
 executing, by the one or more designated tasks, the registered callback function associated with the trigger, wherein the registered callback function, when executed, alters functionality of the code at runtime without requiring recompilation of the code with tracing enabled; and 
 returning, from the one or more designated tasks to the daemon, execution results of the registered callback function, wherein the code includes an application and one or more shared libraries and the registered callback function performs a debugging function. 
 
     
     
       2. The method of  claim 1 , further comprising:
 registering the callback function with a low-level application programming interface (LAPI) using a LAPI utility, wherein a control thread that is created at LAPI initialization invokes the callback function and facilitates communication between the one or more designated tasks and the daemon when the trigger is detected by the control thread. 
 
     
     
       3. The method of  claim 1 , wherein the trigger has an associated trigger name, a job identification, and one or more trigger arguments. 
     
     
       4. The method of  claim 1 , further comprising:
 communicating the execution results from the daemon to the outside process. 
 
     
     
       5. A computer program product for debugging code during runtime embodied on a tangible computer-readable storage memory device, wherein the computer program product, when executed by a data processing system, is configured to:
 receive, from an outside process, a trigger at a daemon, wherein the trigger is associated with a registered callback function; 
 provide, from the daemon, the trigger to one or more designated tasks of a job; 
 execute, by the one or more designated tasks, the registered callback function associated with the trigger, wherein the registered callback function, when executed, alters functionality of the code at runtime without requiring recompilation of the code with tracing enabled; and 
 return, from the one or more designated tasks to the daemon, execution results of the registered callback function, wherein the code includes an application and one or more shared libraries and the registered callback function performs a debugging function. 
 
     
     
       6. The computer program product of  claim 5 , wherein the computer program product, when executed, is further configured to:
 register the callback function with a low-level application programming interface (LAPI) using a LAPI utility, wherein a control thread that is created at LAPI initialization invokes the callback function and facilitates communication between the one or more designated tasks and the daemon when the trigger is detected by the control thread. 
 
     
     
       7. The computer program product of  claim 5 , wherein the trigger has an associated trigger name, a job identification, and one or more trigger arguments. 
     
     
       8. The computer program product of  claim 5 , wherein the computer program product, when executed, is further configured to:
 communicate the execution results from the daemon to the outside process. 
 
     
     
       9. A computer system, comprising:
 a memory subsystem configured to store code; and 
 one or more processors coupled to the memory subsystem, wherein the one or more processors are configured to: 
 receive, from an outside process, a trigger at a daemon, wherein the trigger is associated with a registered callback function; 
 provide, from the daemon, the trigger to one or more designated tasks of a job; 
 execute, by the one or more designated tasks, the registered callback function associated with the trigger, wherein the registered callback function, when executed, alters functionality of the code at runtime without requiring recompilation of the code with tracing enabled; and 
 return, from the one or more designated tasks to the daemon, execution results of the registered callback function, wherein the code includes an application and one or more shared libraries and the registered callback function performs a debugging function. 
 
     
     
       10. The computer system of  claim 9 , wherein the one or more processors are further configured to:
 register the callback function with a low-level application programming interface (LAPI) using a LAPI utility, wherein a control thread that is created at LAPI initialization invokes the callback function and facilitates communication between the one or more designated tasks and the daemon when the trigger is detected by the control thread. 
 
     
     
       11. The computer system of  claim 9 , wherein the trigger has an associated trigger name, a job identification, and one or more trigger arguments.