Debugging computer programming code in a cloud debugger environment

• US 9,262,300 B1
• Filed: 03/19/2015
• Issued: 02/16/2016
• Est. Priority Date: 06/24/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Haba, Erez, Lifliand, Vladimir, Kultursay, Emre, Horowitz, Amnon Omri
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US14/662,282
• Time in Patent Office: 334 Days
• Field of Search: 717123-130, 717140-141
• US Class Current: 1/1
• CPC Class Codes: G06F 11/362 Software debugging
• 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

Abstract

A method for capturing breakpoint information from a debuggee software process includes generating a breakpoint condition based upon a breakpoint request received from a user computing device corresponding to a user and transmitting the generated breakpoint condition to debuglets, each corresponding to a software process executed by a debuggee service. The debuggee service executes on a distributed system, and each debuglet translates the generated breakpoint condition to a physical breakpoint condition set to the respective software process. The method also includes receiving a request from one of the debuglets to update active breakpoint information captured by the debuglet upon the physical breakpoint condition being hit by one of the software processes and transmitting a notification from the processing device indicating the physical breakpoint condition being hit to the user computing device.

Claims

1. A method for capturing breakpoint information from a debuggee software process, the method comprising:

receiving, at a processing device, a breakpoint request from a user computing device in communication with the processing device;

generating, by the processing device, a new breakpoint condition based upon the breakpoint request received from the user computing device, the new breakpoint condition identifying a point in software code run by a debuggee service executing a collection of software processes on a distributed system;

transmitting the new breakpoint condition from the processing device to debuglets of the debuggee service, each debuglet associated with a respective one of the software processes and in communication with the processing device, the new breakpoint condition causing each debuglet to translate the new breakpoint condition to a physical breakpoint condition set to the respective software process;

when one of the software processes hits the physical breakpoint condition;

receiving, at the processing device, a request from the debuglet associated with the software process that hit the physical breakpoint condition to update active breakpoint information captured by the associated debuglet; and

transmitting a notification indicating the hit physical breakpoint condition to the user computing device and each debuglet of the debuggee service, the notification causing the debuglets to remove the previously set physical breakpoint condition from their respective software processes.

2. The method of claim 1, further comprising:

prior to generating the breakpoint condition based upon the breakpoint request;

receiving, at the processing device, a user identifier included with the breakpoint request; and

authorizing, at the processing device, user access rights to capture the active breakpoint information from the debuggee software processes using the user identifier.

3. The method of claim 1, wherein only execution of the respective software process that hit the physical breakpoint condition is stopped for only a period of time sufficient for the respective debuglet to capture the active breakpoint information.

4. The method of claim 3, wherein execution of the respective software process is immediately resumed after the active breakpoint information is captured.

5. The method of claim 1, wherein each debuglet translates the generated breakpoint condition to a specific programming language and executable with the associated respective software process.

6. The method of claim 1, wherein each of the debuglets are dependent upon a programming language of their respective software process.

7. The method of claim 1, wherein receiving the request from one of the debuglets to update active breakpoint information further comprises receiving breakpoint information corresponding to the hit physical breakpoint condition.

8. The method of claim 7, wherein one of the debuglets translates the breakpoint information prior to transmittance to the processing device.

9. The method of claim 1, further comprising storing the breakpoint condition and the captured active breakpoint information in non-transitory memory.

10. A distributed system comprising:

one or more debugger service processing devices executing a debugger service, the debugger service generating a new breakpoint condition based upon a breakpoint request received from a user computing device in communication with the distributed system and corresponding to a user, the new breakpoint condition identifying a point in software code run by a debuggee service executing a collection of software processes; and

one or more debuglet controller processing devices in communication with the one or more debugger service processing devices and executing a debuglet controller, the debuglet controller;

transmitting the generated new breakpoint condition to debuglets of the debuggee service, each debuglet associated with a respective one of the software processes, the new breakpoint condition causing each debuglet to translate the new breakpoint condition to a physical breakpoint condition set to the respective software process;

when one of the software processes hits the physical breakpoint condition;

receiving a request from the debuglet associated with the software process that hit the physical breakpoint condition to update active breakpoint information captured by the associated debuglet; and

transmitting a notification indicating the hit physical breakpoint condition to the user computing device and each debuglet of the debuggee service, the notification causing the debuglets to remove the previously set physical breakpoint condition from their respective software processes.

11. The system of claim 10, wherein the debuglet controller stops execution of only the respective software process that hit the physical breakpoint condition only for a period of time sufficient for the respective debuglet to capture the active breakpoint information.

12. The system of claim 11, wherein the debuglet controller resumes execution of the respective software process immediately after the active breakpoint information is captured.

13. The system of claim 10, wherein, prior to generating the breakpoint condition, the debugger service:

receives a user identifier included with the breakpoint request; and

authorizes user access rights to capture the active breakpoint information from the debuggee software processes using the user identifier.

14. The system of claim 10, further comprising a breakpoint store in communication with the one or more debugger service processing devices and the one or more debuglet controller processing devices, the breakpoint store storing the new breakpoint condition generated by the debugger service and the active breakpoint information captured by the respective debuglet upon the physical breakpoint condition being hit.

15. The system of claim 10, wherein the debugger service receives the breakpoint request from an integrated development environment executing on the user computing device.

16. The system of claim 10, wherein the debugger service includes a debugger application programming interface for setting a breakpoint, retrieving a breakpoint, deleting a breakpoint, and listing breakpoints.

17. The system of claim 10, wherein the debuglet controller includes a debuglet controller application programming interface that enables the debuglets to register their respective debuggees, query for active breakpoints to set, and update active breakpoint information.

18. The system of claim 10, wherein receiving the request from one of the debuglets to update active breakpoint information further comprises receiving breakpoint information corresponding to the hit physical breakpoint condition.