Collaborative software debugging in a distributed system with client-specific event alerts

• US 9,411,709 B2
• Filed: 11/10/2010
• Issued: 08/09/2016
• Est. Priority Date: 11/10/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bates, Cary L.
• Primary Examiner(s): Wu, Daxin
• Application Number:
  US12/943,581
• Publication Number:
  US 20120117542A1
• Time in Patent Office: 2,099 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

In a distributed system including a debug server and debug clients coupled for data communications through a network, where the debug server includes a debug administrator, message router, back-end debugger, and a debuggee, collaborative software debugging includes: presenting a client-specific GUI; detecting user input through the GUI, including user input specifying a location to establish an event; establishing a client-specific event alert to be invoked upon receipt of an event notification for the event; generating application-level messages, including a request to establish the event; sending application-level messages to the debug server, including the request; receiving client-specific debug results, including an event notification for the event; and displaying the client-specific debug results, including invoking the client-specific event alert responsive to the event notification, without invoking an alert by at least one of the other debug clients receiving the event notification.

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:

presenting, by each debug client to a user of the debug client, a client-specific graphical user interface (‘

GUI’

), the client-specific GUI comprising a client-specific display of a debug session of the debuggee;

detecting, by each debug client, user input through the client-specific GUI, including detecting, by a requesting debug client, user input specifying a location in source code to establish an event notification for an event;

establishing, by the requesting debug client, a client-specific event alert to be invoked upon receipt of the event notification;

generating, by each debug client in dependence upon the detected user input, one or more application-level messages, including generating, by the requesting debug client, a request to establish the event notification;

sending, by each debug client, the application-level messages to the debug server, including sending, by the requesting debug client, the request to establish the event notification;

receiving, by each debug client responsive to the application-level messages, client-specific debug results, including receiving, by the requesting debug client and at least one other debug client, the event notification responsive to the back-end debugger encountering the event; and

displaying, by each debug client in the client-specific GUI, the client-specific debug results, including invoking, by the requesting debug client, the client-specific event alert responsive to the event notification, without invoking an alert by at least one of the other debug clients receiving the event notification.

2. The method of claim 1 wherein detecting user input through the client-specific GUI further comprises receiving user input enabling the client-specific event alert to be invoked upon receipt of an event notification for the event established by the requesting debug client.

3. The method of claim 1 further comprising receiving user input disabling the client-specific event alert.

4. The method of claim 1 further comprising receiving user input enabling the client-specific event alert to be invoked upon receipt of an event notification for an intervening event not established by the requesting debug client.

5. The method of claim 1 wherein invoking the client-specific event alert further comprises displaying, in the client-specific GUI, a visual notification.

6. The method of claim 1 wherein invoking the client-specific event alert further comprises playing an audible notification.

7. 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:

presenting, by each debug client to a user of the debug client, a client-specific graphical user interface (‘

GUI’

), the client-specific GUI comprising a client-specific display of a debug session of the debuggee;

detecting, by each debug client, user input through the client-specific GUI, including detecting, by a requesting debug client, user input specifying a location in source code to establish an event notification for an event;

establishing, by the requesting debug client, a client-specific event alert to be invoked upon receipt of the event notification;

generating, by each debug client in dependence upon the detected user input, one or more application-level messages, including generating, by the requesting debug client, a request to establish the event notification;

sending, by each debug client, the application-level messages to the debug server, including sending, by the requesting debug client, the request to establish the event notification;

receiving, by each debug client responsive to the application-level messages, client-specific debug results, including receiving, by the requesting debug client and at least one other debug client, the event notification responsive to the back-end debugger encountering the event; and

displaying, by each debug client in the client-specific GUI, the client-specific debug results, including invoking, by the requesting debug client, the client-specific event alert responsive to the event notification, without invoking an alert by at least one of the other debug clients receiving the event notification.

8. The apparatus of claim 7 wherein detecting user input through the client-specific GUI further comprises receiving user input enabling the client-specific event alert to be invoked upon receipt of an event notification for the event established by the requesting debug client.

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 user input disabling the client-specific event alert.

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 user input enabling the client-specific event alert to be invoked upon receipt of an event notification for an intervening event not established by the requesting debug client.

11. The apparatus of claim 7 wherein invoking the client-specific event alert further comprises displaying, in the client-specific GUI, a visual notification.

12. The apparatus of claim 7 wherein invoking the client-specific event alert further comprises playing an audible notification.

13. 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, wherein the computer readable storage medium is not a signal, 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 steps of:

presenting, by each debug client to a user of the debug client, a client-specific graphical user interface (‘

GUI’

), the client-specific GUI comprising a client-specific display of a debug session of the debuggee;

detecting, by each debug client, user input through the client-specific GUI, including detecting, by a requesting debug client, user input specifying a location in source code to establish an event notification for an event;

establishing, by the requesting debug client, a client-specific event alert to be invoked upon receipt of the event notification;

generating, by each debug client in dependence upon the detected user input, one or more application-level messages, including generating, by the requesting debug client, a request to establish the event notification;

sending, by each debug client, the application-level messages to the debug server, including sending, by the requesting debug client, the request to establish the event notification;

receiving, by each debug client responsive to the application-level messages, client-specific debug results, including receiving, by the requesting debug client and at least one other debug client, the event notification responsive to the back-end debugger encountering the event; and

displaying, by each debug client in the client-specific GUI, the client-specific debug results, including invoking, by the requesting debug client, the client-specific event alert responsive to the event notification, without invoking an alert by at least one of the other debug clients receiving the event notification.

14. The computer program product of claim 13 wherein detecting user input through the client-specific GUI further comprises receiving user input enabling the client-specific event alert to be invoked upon receipt of an event notification for the event established by the requesting debug client.

15. The computer program product of claim 13 further comprising computer program instructions that, when executed by the computer processor, cause the computer to carry out the step of receiving user input disabling the client-specific event alert.

16. The computer program product of claim 13 further comprising computer program instructions that, when executed by the computer processor, cause the computer to carry out the step of receiving user input enabling the client-specific event alert to be invoked upon receipt of an event notification for an intervening event not established by the requesting debug client.

17. The computer program product of claim 13 wherein invoking the client-specific event alert further comprises displaying, in the client-specific GUI, a visual notification.

18. The computer program product of claim 13 wherein invoking the client-specific event alert further comprises playing an audible notification.