Collaborative Software Debugging In A Distributed System With Stacked Event Group Management

• US 20120102459A1
• Filed: 10/20/2010
• Published: 04/26/2012
• Est. Priority Date: 10/20/2010
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bates, Cary L.
• Application Number:
  US12/908,223
• Publication Number:
  US 20120102459A1
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving, from the debug clients, application-level messages, including multiple requests to establish an event notification; routing the messages among the debug clients, debug administrator, and back-end debugger, including forwarding each request to the debug administrator, and forwarding only one of the requests to the back-end debugger; establishing one event notification; assigning, for each request, the event notification to an event group, each event group associated with one of the requesting debug clients; and returning client-specific debug results including sending, to each of the requesting debug clients, an event notification upon the back-end debugger encountering the event at the location in source code.

Claims

1. A method of collaborative software debugging in a distributed system, the distributed system comprising a debug server, a plurality of debug clients, and a data communications network, the debug server coupled for data communications to the plurality of debug clients through the data communications network, the debug server comprising a debug administrator, a message router, a back-end debugger, and a debuggee, the method comprising:

receiving, by the debug server from the debug clients asynchronously during a debug session of the debuggee, a plurality of application-level messages, including receiving, separately from two or more requesting debug clients, a request to establish an event notification at a location in source code of the debuggee;

routing, by the message router in accordance with an application-level message passing protocol, the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger to the debug clients with application-level messages routed to the back-end debugger, forwarding each request to the debug administrator, and forwarding only one of the requests to the back-end debugger;

establishing, by the back-end debugger, one event notification at the location in source code;

assigning, by the debug administrator for each request, the event notification to an event group, each event group associated with one of the requesting debug clients; and

returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results including sending, in dependence upon the event groups to each of the requesting debug clients, an event notification upon the back-end debugger encountering the event at the location in source code.

2. The method of claim 1, further comprising managing, by the debug server during the debug session, event notifications in dependence upon event groups.

3. The method of claim 2, further comprising:

receiving, by the message router from a particular debug client, a request to remove the established event notification, wherein managing event notifications further comprises;

determining whether any event group other than the particular debug client'"'"'s event group includes the established event notification;

if any event group other than the particular debug client'"'"'s event group includes the established event notification, removing the established event notification from the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if no event group other than the particular debug client'"'"'s event group includes the established event notification, forwarding, by the message router to the back-end debugger, a command to remove the established event and removing the established event notification from the requesting debug client'"'"'s event group.

4. The method of claim 2, further comprising:

receiving, by the message router from a particular debug client, a request to disable the established event notification, wherein managing event notifications further comprises;

determining whether any event group other than the particular debug client'"'"'s event group includes the established event notification;

if any event group other than the particular debug client'"'"'s event group includes the established event notification, disabling the established event notification only in the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if no event group other than the particular debug client'"'"'s event group includes the established event notification, forwarding, by the message router to the back-end debugger, a command to disable the established event and disabling the established event in the particular debug client'"'"'s event group.

5. The method of claim 2, further comprising:

receiving, by the message router from a particular debug client, a request to enable the established event notification, wherein managing event notifications further comprises;

determining whether the established event notification is enabled in at least one event group;

if the established event notification is enabled in at least one event group, enabling the established event notification in the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if the established event notification is not enabled in at least one event group, forwarding, by the message router to the back-end debugger, a command to enable the established event and enabling the established event in the particular debug client'"'"'s event group.

6. An apparatus for collaborative software debugging in a distributed system, the distributed system comprising a debug server, a plurality of debug clients, and a data communications network, the debug server coupled for data communications to the plurality of debug clients through the data communications network, the debug server comprising a debug administrator, a message router, a back-end debugger, and a debuggee, the apparatus comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of:

receiving, by the debug server from the debug clients asynchronously during a debug session of the debuggee, a plurality of application-level messages, including receiving, separately from two or more requesting debug clients, a request to establish an event notification at a location in source code of the debuggee;

routing, by the message router in accordance with an application-level message passing protocol, the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger to the debug clients with application-level messages routed to the back-end debugger, forwarding each request to the debug administrator, and forwarding only one of the requests to the back-end debugger;

establishing, by the back-end debugger, one event notification at the location in source code;

assigning, by the debug administrator for each request, the event notification to an event group, each event group associated with one of the requesting debug clients; and

returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results including sending, in dependence upon the event groups to each of the requesting debug clients, an event notification upon the back-end debugger encountering the event at the location in source code.

7. The apparatus of claim 6, further comprising computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the step of managing, by the debug server during the debug session, event notifications in dependence upon event groups.

8. The apparatus of claim 7, further comprising computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the step of:

receiving, by the message router from a particular debug client, a request to remove the established event notification, wherein managing event notifications further comprises;

determining whether any event group other than the particular debug client'"'"'s event group includes the established event notification;

if any event group other than the particular debug client'"'"'s event group includes the established event notification, removing the established event notification from the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if no event group other than the particular debug client'"'"'s event group includes the established event notification, forwarding, by the message router to the back-end debugger, a command to remove the established event and removing the established event notification from the requesting debug client'"'"'s event group.

9. The apparatus of claim 7, further comprising computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the step of:

receiving, by the message router from a particular debug client, a request to disable the established event notification, wherein managing event notifications further comprises;

determining whether any event group other than the particular debug client'"'"'s event group includes the established event notification;

if any event group other than the particular debug client'"'"'s event group includes the established event notification, disabling the established event notification only in the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if no event group other than the particular debug client'"'"'s event group includes the established event notification, forwarding, by the message router to the back-end debugger, a command to disable the established event and disabling the established event in the particular debug client'"'"'s event group.

10. The apparatus of claim 7, further comprising computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the step of:

receiving, by the message router from a particular debug client, a request to enable the established event notification, wherein managing event notifications further comprises;

determining whether the established event notification is enabled in at least one event group;

if the established event notification is enabled in at least one event group, enabling the established event notification in the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if the established event notification is not enabled in at least one event group, forwarding, by the message router to the back-end debugger, a command to enable the established event and enabling the established event in the particular debug client'"'"'s event group.

11. A computer program product for collaborative software debugging in a distributed system, the distributed system comprising a debug server, a plurality of debug clients, and a data communications network, the debug server coupled for data communications to the plurality of debug clients through the data communications network, the debug server comprising a debug administrator, a message router, a back-end debugger, and a debuggee, the computer program product disposed upon a computer readable storage medium, the computer program product comprising computer program instructions that, when executed by a computer processor of a computer, cause the computer to carry out the step of:

receiving, by the debug server from the debug clients asynchronously during a debug session of the debuggee, a plurality of application-level messages, including receiving, separately from two or more requesting debug clients, a request to establish an event notification at a location in source code of the debuggee;

routing, by the message router in accordance with an application-level message passing protocol, the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger to the debug clients with application-level messages routed to the back-end debugger, forwarding each request to the debug administrator, and forwarding only one of the requests to the back-end debugger;

establishing, by the back-end debugger, one event notification at the location in source code;

assigning, by the debug administrator for each request, the event notification to an event group, each event group associated with one of the requesting debug clients; and

returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results including sending, in dependence upon the event groups to each of the requesting debug clients, an event notification upon the back-end debugger encountering the event at the location in source code.

12. The computer program product of claim 11, further comprising computer program instructions that, when executed by the computer processor, cause the computer to carry out the step of managing, by the debug server during the debug session, event notifications in dependence upon event groups.

13. The computer program product of claim 12, further comprising computer program instructions that, when executed by the computer processor, cause the computer to carry out the step of:

receiving, by the message router from a particular debug client, a request to remove the established event notification, wherein managing event notifications further comprises;

determining whether any event group other than the particular debug client'"'"'s event group includes the established event notification;

if any event group other than the particular debug client'"'"'s event group includes the established event notification, removing the established event notification from the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if no event group other than the particular debug client'"'"'s event group includes the established event notification, forwarding, by the message router to the back-end debugger, a command to remove the established event and removing the established event notification from the requesting debug client'"'"'s event group.

14. The computer program product of claim 12, further comprising computer program instructions that, when executed by the computer processor, cause the computer to carry out the step of:

receiving, by the message router from a particular debug client, a request to disable the established event notification, wherein managing event notifications further comprises;

determining whether any event group other than the particular debug client'"'"'s event group includes the established event notification;

if any event group other than the particular debug client'"'"'s event group includes the established event notification, disabling the established event notification only in the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if no event group other than the particular debug client'"'"'s event group includes the established event notification, forwarding, by the message router to the back-end debugger, a command to disable the established event and disabling the established event in the particular debug client'"'"'s event group.

15. The computer program product of claim 12, further comprising computer program instructions that, when executed by the computer processor, cause the computer to carry out the step of:

receiving, by the message router from a particular debug client, a request to enable the established event notification, wherein managing event notifications further comprises;

determining whether the established event notification is enabled in at least one event group;

if the established event notification is enabled in at least one event group, enabling the established event notification in the particular debug client'"'"'s event group without forwarding any command to the back-end debugger; and

if the established event notification is not enabled in at least one event group, forwarding, by the message router to the back-end debugger, a command to enable the established event and enabling the established event in the particular debug client'"'"'s event group.

16. The computer program product of claim 11, wherein the computer readable storage medium further comprises a transmission medium.

17. The computer program product of claim 11, wherein the computer readable storage medium further comprises a recordable medium.