Remote debugging proxy

Abstract

A system and method for a remote debugging proxy. An embodiment of a method for debugging a target system application includes receiving notification of an event regarding the target system at a first proxy component via a second proxy component. The method further includes receiving data regarding the event at the first proxy component via the second proxy component, and storing the data in a cache memory.

1 - 24 . (canceled)  
     
     
         25 . A method for debugging a target system application comprising: 
 receiving notification of an event regarding the target system at a first proxy component via a second proxy component;    receiving data regarding the event at the first proxy component via the second proxy component; and    storing the data in a cache memory.    
     
     
         26 . The method of  claim 25 , further providing forwarding the notification of the event to a debugging component.  
     
     
         27 . The method of  claim 26 , further comprising: 
 receiving a request from the debugging component for information regarding the target system; and    searching the cache memory for the requested information.    
     
     
         28 . The method of  claim 27 , further comprising transferring the requested information to the debugging component if the information is present in the cache memory.  
     
     
         29 . The method of  claim 28 , wherein the requested information is provided to the debugging component without sending a communication to the target system.  
     
     
         30 . The method of  claim 27 , further comprising transferring the request to the target system via the second proxy component if the information is not present in the cache memory.  
     
     
         31 . The method of  claim 25 , wherein receiving data regarding the event at the first proxy component via the second proxy component includes decompressing the received data.  
     
     
         32 . The method of  claim 25 , wherein the target system comprises a Java virtual machine.  
     
     
         33 . A debugging proxy comprising: 
 a first connector to be coupled with a debugger;    a second connector to be coupled with a proxy for a target computer system to be debugged; and    a memory to hold data regarding events of the target computer system received from the proxy for the target computer system.    
     
     
         34 . The debugging proxy of  claim 33 , further comprising an input controller to receive a request for data from the debugger via the first connector.  
     
     
         35 . The debugging proxy of  claim 34 , wherein the input controller is to search the memory for the requested data.  
     
     
         36 . The debugging proxy of  claim 35 , wherein the input controller is to direct the requested data to the debugger via the first connector if the requested data is present in the memory.  
     
     
         37 . The debugging proxy of  claim 35 , wherein the input controller is to direct the request from data to the second proxy via the second connector if the requested data is not present in the memory.  
     
     
         38 . The debugging proxy of  claim 33 , further comprising an output controller to receive commands via the second connector.  
     
     
         39 . The debugging proxy of  claim 38 , wherein if the command comprises a event regarding the target system then the output controller directs the event to the debugger via the first connector.  
     
     
         40 . The debugging proxy of  claim 38 , wherein if the command comprises data regarding an event of the target system then the output controller directs the data to the memory for storage.  
     
     
         41 . The debugging proxy of  claim 33 , wherein the first connector and the second connector comprise JDI (Java debug interface) connectors.  
     
     
         42 . A debugging system comprising: 
 a debugging component;    a first proxy component coupled with the debugging component;    a memory coupled with the first proxy component for storage of data regarding events of a target computing system, and    a link with a second proxy component, the first proxy component to receive event notifications from the target computing system and data regarding events of the target computing system via the second proxy component.    
     
     
         43 . The debugging system of  claim 42 , wherein the first proxy component is to search the memory upon receiving a request for data from the debugging component.  
     
     
         44 . The debugging system of  claim 43 , wherein the first proxy component directs the requested data to the debugging component if the requested data is present in the memory and directs the request for data to the target system if the requested data is not present in the memory.  
     
     
         45 . The debugging system of  claim 42 , further comprising a user interface for making the request for data.  
     
     
         46 . The debugging system of  claim 42 , wherein the debugging system is a Java platform debugger architecture (JPDA) system.  
     
     
         47 . The debugging system of  claim 42 , wherein the first proxy component communicates with the second proxy component communicate using Java debug wire protocol (JDWP).  
     
     
         48 . A machine-readable medium having stored thereon data representing sequences of instructions that, when executed by a processor, cause the processor to perform operations comprising: 
 receiving notification of an event regarding a target computing system;    receiving data regarding the event;    storing the data regarding the event;    receiving a request for data regarding the event from a debugging component; and    determining whether the requested data is stored.    
     
     
         49 . The medium of  claim 48 , further comprising instructions that, when executed by a processor, cause the processor to perform operations comprising: 
 if the data is stored, sending a reply containing the stored data to the debugging component; and    if the data is not stored, sending the data request to the target computing system.    
     
     
         50 . The medium of  claim 49 , wherein receiving notification of the event includes receiving the notification at a proxy for the debugging component.  
     
     
         51 . The medium of  claim 50 , wherein sending the data request to the target computing system includes providing the data request to a proxy for the target computing system.  
     
     
         52 . The medium of  claim 48 , wherein storing the data regarding the event comprises storing the data in a cache memory.