Collaborative software debugging in a distributed system with dynamically displayed chat sessions

• US 8,990,775 B2
• Filed: 11/10/2010
• Issued: 03/24/2015
• 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): Bullock, Jr., Lewis A
• Assistant Examiner(s): Huynh, Tina
• Application Number:
  US12/943,339
• Publication Number:
  US 20120117541A1
• Time in Patent Office: 1,595 Days
• Field of Search: 717/124, 709204-207
• US Class Current: 717/125
• CPC Class Codes: G06F 11/362 Software debugging
• 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
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]

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 application-level messages, including receiving, a request to establish a chat session associated with a location in source code of the debuggee; routing the application-level messages among the debug clients, the debug administrator, and the back-end debugger; returning client-specific debug results, including sending, to the debug clients, a notification of an established chat session; and administering, by the message router, chat content for the established chat session among debug clients. Debug clients display the chat content in a chat box at the location in source code when the view of source code includes the location.

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 plurality of debug clients asynchronously during a debug session of the debuggee, a plurality of application-level messages, including receiving a request to establish a chat session associated with a location in source code of the debuggee, wherein the request to establish the chat session includes a payload that identifies the location in the source code;

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

returning, by the debug server to the plurality of debug clients in response to the plurality of application-level messages routed to the back-end debugger, client-specific debug results, including sending, to the plurality of debug clients, a notification of the established chat session at the location in the source code; and

administering, by the message router, chat content for the established chat session among the plurality of debug clients, including dynamically displaying, by each debug client, when a current view of the source code by a particular debug client includes the location, a chat interface configured for receiving user input comprising the chat content, wherein the chat interface is presented at the location in the source code.

2. The method of claim 1 wherein:

routing the plurality of application-level messages further comprises forwarding to the debug administrator the request to establish the chat session; and

the method further comprises registering, by the debug administrator, the chat session including assigning a chat identifier to the chat session and returning the chat identifier to the message router.

3. The method of claim 1 wherein receiving the request to establish the chat session associated with the location in the source code of the debuggee further comprises receiving an application-level message having a DISTRIBUTE REQUEST message type and the payload including the location in the source code and, optionally, the chat content.

4. The method of claim 1 wherein sending, to the plurality of debug clients, the notification of the established chat session at the location in the source code further comprises sending an application-level message having a REQUEST REPLY message type and the payload that includes an indication of the established chat session, the location in the source code of the established chat session, and, optionally, the chat content.

5. The method of claim 1 wherein administering the chat content for the established chat session among the plurality of debug clients further comprises receiving an application-level message having a DISTRIBUTE REQUEST message type, an identification of one or more recipients, and the payload comprising the location in the source code and the chat content.

6. The method of claim 1 wherein administering the chat content for the established chat session among the plurality of debug clients further comprises sending, to the plurality of debug clients in response to the request to distribute the chat content, an application-level message having a REPLY REQUEST message type and the payload that includes the location in the source code and the chat content.

7. 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 each 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 the each debug client, user input through the client-specific GUI, including the detecting user input to establish a chat session at a location in source code;

generating, by the each debug client in dependence upon the detected user input, one or more application-level messages, including generating a request to establish the chat session at the location in the source code, wherein the request to establish the chat session includes a payload that identifies the location in the source code;

sending, by the each debug client, the application-level messages to the debug server, including sending the request to establish the chat session;

receiving, by the each debug client responsive to the one or more application-level messages, client-specific debug results, including receiving, by the plurality of debug clients, a notification of the established chat session at the location in the source code; and

displaying, by the each debug client in the client-specific GUI, the client-specific debug results, including dynamically displaying, by the each debug client, when a current view of the source code by a particular debug client includes the location, a chat interface configured for receiving user input comprising chat content, wherein the chat interface is presented at the location in the source code.

8. The method of claim 7 wherein generating the request to establish the chat session at the location in the source code further comprises generating an application-level message having a DISTRIBUTE REQUEST message type and the payload including the location in the source code and, optionally, the chat content.

9. The method of claim 7 wherein receiving, by the plurality of debug clients, the notification of the established chat session at the location in the source code further comprises receiving an application-level message having a REQUEST REPLY message type and the payload that includes an indication of the established chat session, the location in the source code of the established chat session, and, optionally, the chat content.

10. The method of claim 7 wherein displaying the chat interface at the location in the source code further comprises displaying the chat interface only if the each debug client has contributed a number of debug operations associated with the location in the source code greater than a predefined threshold within a predefined period of time.

11. The method of claim 7, further comprising:

distributing, by the each debug client via the debug server to other debug clients, the chat content received as user input in the each debug client'"'"'s chat interface displayed at the location in the source code; and

displaying, by the each debug client in the chat interface at the location in the source code, the chat content received from the other debug clients via the debug server.

12. The method of claim 11, wherein distributing the chat content to other debug clients further comprises sending to the debug server an application-level message having a DISTRIBUTE REQUEST message type, an identification of one or more recipients, and the payload comprising the location in the source code and the chat content.

13. The method of claim 11, wherein displaying the chat content received from other debug clients via the debug server further comprises receiving an application-level message having a REPLY REQUEST message type and the payload that includes the location in the source code and the chat content.

14. 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 each 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 the each debug client, user input through the client-specific GUI, including the detecting user input to establish a chat session at a location in source code;

generating, by the each debug client in dependence upon the detected user input, one or more application-level messages, including generating a request to establish the chat session at the location in the source code, wherein the request to establish the chat session includes a payload that identifies the location in the source code;

sending, by the each debug client, the one or more application-level messages to the debug server, including sending the request to establish the chat session;

receiving, by the each debug client responsive to the one or more application-level messages, client-specific debug results, including receiving, by the plurality of debug clients, a notification of the established chat session at the location in the source code; and

displaying, by the each debug client in the client-specific GUI, the client-specific debug results, including dynamically displaying, by the each debug client, when a current view of the source code by a particular debug client includes the location, a chat interface configured for receiving user input comprising chat content, wherein the chat interface is presented at the location in the source code.

15. The apparatus of claim 14 wherein generating the request to establish the chat session at the location in the source code further comprises generating an application-level message having a DISTRIBUTE REQUEST message type and the payload including the location in the source code and, optionally, the chat content.

16. The apparatus of claim 14 wherein receiving, by the plurality of debug clients, the notification of the established chat session at the location in the source code further comprises receiving an application-level message having a REQUEST REPLY message type and the payload that includes an indication of the established chat session, the location in the source code of the established chat session, and, optionally, the chat content.

17. The apparatus of claim 14 wherein displaying the chat interface at the location in the source code further comprises displaying the chat interface only if the each debug client has contributed a number of debug operations associated with the location in the source code greater than a predefined threshold within a predefined period of time.

18. The apparatus of claim 14, further comprising computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of:

distributing, by the each debug client via the debug server to other debug clients, the chat content received as user input in the debug client'"'"'s chat interface displayed at the location in the source code; and

displaying, by the each debug client in the chat interface at the location in the source code, the chat content received from the other debug clients via the debug server.

19. The apparatus of claim 18, wherein distributing the chat content to other debug clients further comprises sending to the debug server an application-level message having a DISTRIBUTE REQUEST message type, an identification of one or more recipients, and the payload comprising the location in the source code and the chat content.

20. The apparatus of claim 18, wherein displaying the chat content received from other debug clients via the debug server further comprises receiving an application-level message having a REPLY REQUEST message type and the payload that includes the location in the source code and the chat content.

21. 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 program product 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 each 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 the each debug client, user input through the client-specific GUI, including the detecting user input to establish a chat session at a location in source code;

generating, by the each debug client in dependence upon the detected user input, one or more application-level messages, including generating a request to establish the chat session at the location in the source code, wherein the request to establish the chat session includes a payload that identifies the location in the source code;

sending, by the each debug client, the one or more application-level messages to the debug server, including sending the request to establish the chat session;

receiving, by the each debug client responsive to the one or more application-level messages, client-specific debug results, including receiving, by the plurality of debug clients, a notification of the established chat session at the location in the source code; and

displaying, by the each debug client in the client-specific GUI, the client-specific debug results, including dynamically displaying, by the each debug client, when a current view of the source code by a particular debug client includes the location, a chat interface configured for receiving user input comprising chat content, wherein the chat interface is presented at the location in the source code.

22. The computer program product of claim 21 wherein receiving, by the plurality of debug clients, the notification of the established chat session at the location in the source code further comprises receiving an application-level message having a REQUEST REPLY message type and the payload that includes an indication of the established chat session, the location in the source code of the established chat session, and, optionally, the chat content.

23. The computer program product of claim 21 wherein displaying the chat interface at the location in the source code further comprises displaying the chat interface only if the each debug client has contributed a number of debug operations associated with the location in the source code greater than a predefined threshold within a predefined period of time.

24. The computer program product of claim 21, further comprising computer program instructions that, when executed by the computer processor, cause the computer to carry out the steps of:

distributing, by the each debug client via the debug server to other debug clients, the chat content received as user input in the each debug client'"'"'s chat interface displayed at the location in the source code; and

displaying, by the each debug client in the chat interface at the location in the source code, the chat content received from the other debug clients via the debug server.