Methods utilizing a debugging proxy

• US 7,530,053 B2
• Filed: 02/26/2004
• Issued: 05/05/2009
• Est. Priority Date: 02/27/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Lucas, Terry Leonard, Eckels, Joshua Moll, Pugh, William A.
• Primary Examiner(s): Zhen; Wei Y
• Assistant Examiner(s): Nguyen; Phillip H
• Application Number:
  US10/787,702
• Publication Number:
  US 20050010678A1
• Time in Patent Office: 1,895 Days
• Field of Search: 717/124
• US Class Current: 717/124
• CPC Class Codes: G06F 11/362 Software debugging

Abstract

A debugging proxy can be used to manage communication between a client and a debugger or debugging component. A debugging protocol can be used by the debugging proxy to facilitate communication management. A debugging protocol can provide for asynchronous messaging, and can allow for the communication of large grain messages. A debugging protocol can also implement a priority scheme that can be used to process messages between a client and a debugger based upon a priority assigned to each message.

Claims

1. A computer-implemented method for communicating between a client and a debugging component located on a remote server through a debugging proxy, comprising:

communicating between the client and the debugging component located on the remote server through a debugging proxy, wherein a user can monitor and control execution of software on the remote server; and

managing communication between the client and the debugging proxy through a debugging protocol, wherein the debugging protocol supports asynchronous messaging and permits coarse grained messages, and the debugging protocol implements a priority scheme to process messages between the client and the debugging component based upon a priority assigned to each message;

wherein the client sends coarse grained messages to the debug proxy using the debugging protocol and the debugging proxy sends fine grained messages to the debugging component on the remote server;

wherein the debugging proxy examines each message, determines a priority, and places the message on a priority queue, wherein priorities are assigned dynamically based on information that changes at run-time, wherein messages requesting information that the user has examined frequently have higher priority than messages requesting information that have been accessed less frequently;

wherein a plurality of worker threads dequeue and process messages from the priority queue starting with the highest priority items first and working through the remaining items when the plurality of worker threads are not processing immediate priority messages;

wherein the debugging proxy creates a worker thread for each coarse grained message and the worker thread generates a corresponding series of fine grained messages to a server conforming to the server'"'"'s standard debugging protocol;

wherein the debugging proxy removes items from the response queue in order and sends them asynchronously to the client; and

wherein communication between the debugging proxy and a native interface of the debugging component is synchronous.

2. The method of claim 1, wherein communication with the debugging component is handled using the debugging component'"'"'s native interface.

3. The method of claim 1, wherein lower priority requests are automatically overridden it associated results are no longer needed by the client.

4. The method of claim 1, wherein the client can send a request and return control to a user, allowing the user to continue interacting with the client and sending commands.

5. The method of claim 4, wherein the client can send several commands without waiting for results to be returned and displayed.

6. The method of claim 5, wherein results are returned to the client asynchronously, allowing the client to update its display with information as the information becomes available, without disrupting responsiveness of the debugging component to the user.

7. The method of claim 3, wherein if the user steps into another function before values of variables are returned, requests for the values of variables can be cancelled.

8. The method of claim 1, wherein the client generates debug requests to the debug proxy in response to the user'"'"'s interaction with a user interface.

9. The method of claim 1, wherein an immediate priority message is sent directly from the debugging proxy to a worker thread.

10. The method of claim 9, wherein an override message causes the debugging proxy to remove all pending requests from the priority queue that have a lower priority than the override message.

11. The method of claim 1, wherein the debugging proxy is located on the same machine as the server.

12. The method of claim 11, wherein the debugging proxy is located in the same process as the debugger component on the server.

13. The method of claim 1, wherein the worker thread aggregates all of the required responses from the server into a single coarse grained message and places the coarse grained message into the response queue.

14. The method of claim 13, wherein a debug listener in the client listens for asynchronous results from the server and notifies a user interface as results are received.

15. The method of claim 14, wherein the user interface updates its display based on new information.

16. The method of claim 15, wherein the server generates an asynchronous response every time a breakpoint is encountered.

17. The method of claim 16, wherein worker threads listen for asynchronous events from the server, package the asynchronous events into coarse grained messages, and send the coarse grained messages to the client.

18. The method of claim 1, wherein the debugging protocol includes request and response messages.

19. The method of claim 18, wherein the request and response messages are implemented by serialized objects.

20. The method of claim 19, wherein each message includes a name, a priority, a yes or no value indicating whether the message overrides lower priority messages previously sent, and optional comments.

21. The method of claim 1, wherein the priority queue is implemented using several individual queues.

22. The method of claim 21, wherein there is one individual queue for each priority.

23. The method of claim 22, wherein the debugging proxy examines the priority for each request message and places the message on the corresponding queue.

24. The method of claim 21, wherein if the debugging proxy receives an override message, the debugging proxy removes all the messages from each queue with a lower priority than the override message.

25. The method of claim 21, wherein worker threads process messages with immediate priority first and subsequently process messages in the queues by priority.

26. The method of claim 25, wherein the worker thread removes and processes the message on the front of the highest priority queue.

27. The method of claim 1, wherein priorities are assigned statically based on message type.

28. The method of claim 1, wherein messages requesting information currently visible in an integrated development environment have higher priority than messages requesting information that is not currently visible.

29. The method of claim 1, wherein the client has an application programming interface for adjusting the default priorities of messages.

30. A memory having instructions stored thereon that, when executed by a processor, cause the processor to communicate between a client and a debugging component located on a remote server through a debugging proxy by:

communicating between the client and the debugging component located on the remote server through a debugging proxy, wherein a user can monitor and control execution of software on the remote server; and

managing communication between the client and the debugging proxy through a debugging protocol, wherein the debugging protocol supports asynchronous messaging and permits coarse grained messages, and the debugging protocol implements a priority scheme to process messages between the client and the debugging component based upon a priority assigned to each message;

wherein the client sends coarse grained messages to the debug proxy using the debugging protocol and the debugging proxy sends fine grained messages to the debugging component on the remote server;

wherein the debugging proxy examines each message, determines a priority, and places the message on a priority queue, wherein priorities are assigned dynamically based on information that changes at run-time, wherein messages requesting information that the user has examined frequently have higher priority than messages requesting information that have been accessed less frequently;

wherein a plurality of worker threads dequeue and process messages from the priority queue starting with the highest priority items first and working through the remaining items when the plurality of worker threads are not processing immediate priority messages;

wherein the debugging proxy creates a worker thread for each coarse grained message and the worker thread generates a corresponding series of fine grained messages to a server conforming to the server'"'"'s standard debugging protocol;

wherein the debugging proxy removes items from the response queue in order and sends them asynchronously to the client; and

wherein communication between the debugging proxy and a native interface of the debugging component is synchronous.