# US 2024/0004780 A1 · Parallel execution during application debugging

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0004780 A1
- Document ID: US20240004780A1
- Status: Published application
- Kind: A1
- Application number: 17/810,294
- Filed: 2022-06-30
- Published: 2024-01-04
- Earliest claimed: 2022-06-30
- Assignees: Amazon Technologies, Inc.
- Applicants: Amazon Technologies, Inc.
- Inventors: Richard Henry Boyd; Jonathan M Henson
- Web page: https://patentgrep.com/patent/US20240004780A1

## CPC

- G06F 11/3632: {of specific synchronisation aspects}
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F 11/3612: {by runtime analysis (performance monitoring G06F11/3466)}
- G06F 11/362: Debugging of software
- G06F 11/3684: {for test design, e.g. generating new test cases}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An application debugger may define multiple unique initial states of execution for an application on behalf of a client. These unique initial states may include unique sets of application variable values. The application debugger may then create respective application runtimes initialized with the respective sets of application variable values. Then, the execution runtimes may be independently executed to a termination condition that may include a defined set of breakpoints, a normal termination or an abnormal termination. The application debugger may then receive termination state information from the respective execution runtimes, provide additional analysis of these termination states and report results to the client.

## Claims

### Claim 1

A system comprising:
a computing node, comprising at least one processor and memory, implementing an application debugger configured to:
receive, from a client via a user interface, respective unique sets of initialization values for different variables defining a plurality of initial states of execution of an application;
create, at a plurality of computing nodes, a plurality of execution runtime s for the application corresponding to respective ones of the plurality of initial states, wherein the plurality of execution environments differ according to the respective unique sets of application parameters;
receive respective sets of completion parameters from the plurality of computing nodes; and
return, to the client via the user interface, one or more unique completion states of execution of the application according to the received sets of completion parameters; and
the plurality of computing nodes, respectively comprising at least one processor and memory, configured to:
execute individual ones of the plurality of execution runtimes to termination according to one or more termination conditions; and
return respective sets of completion parameters to the application debugger.

### Claim 2 (depends on 1)

The system of claim 1, wherein the application debugger is provided as part of an application development service of a provider network, wherein the plurality of computing nodes implement a compute service of the provider network, and wherein the plurality of execution runtimes are created using respective virtual machines of the compute service of the provider network.

### Claim 3 (depends on 1)

The system of claim 1, wherein the application debugger executes interactively on behalf of the client, and wherein the plurality of execution runtimes respectively execute non-interactively on behalf of the application debugger.

### Claim 4 (depends on 1)

The system of claim 1, wherein the execution coordinator executes non-interactively, wherein the plurality of initial states of execution of the application define a test case for a phase of a software testing life cycle; and wherein the one or more unique completion states of execution of the application comprise at least a passing completion state and a failing completion state.

### Claim 5

A method, comprising:
receiving, at an execution coordinator from a client via a programmatic interface, respective unique sets of application parameters defining a plurality of initial states of execution of an application;
creating a plurality of execution runtimes for the application corresponding to respective ones of the plurality of initial states, wherein the plurality of execution environments differ according to the respective unique sets of application parameters;
executing individual ones of the plurality of execution runtimes to termination according to one or more termination conditions; and
returning, by the execution coordinator to the client via the programmatic interface, respective sets of completion parameters defining one or more unique completion states of execution of the application.

### Claim 6 (depends on 5)

The method of claim 5, wherein the execution coordinator is an application debugger, wherein the sets of application parameters comprise respective sets of initialization values for different variables of the application, and wherein the one or more termination conditions comprise execution breakpoints.

### Claim 7 (depends on 6)

The method of claim 6, wherein a number of unique completion states of execution of the application is fewer than a number of unique initial states of execution of the application, and wherein the method further comprises:
analyzing the unique completion states of execution of the application to identify a portion of the unique initial states of execution of the application corresponding to the unique completion states of execution of the application; and
returning, by the execution coordinator to the client via the programmatic interface, the portion of the unique initial states of execution of the application.

### Claim 8 (depends on 7)

The method of claim 7, further comprising:
selecting respective additional unique sets of application parameters defining a second plurality of initial states of execution of an application according to the completion parameters defining the one or more unique completion states of execution of the application;
creating a second plurality of execution runtimes for the application corresponding to respective ones of the second plurality of initial states, wherein the second plurality of execution environments differ according to the respective additional unique sets of application parameters;
individually executing the second plurality of execution runtimes to termination according to one or more additional termination conditions; and
returning, by the execution coordinator to the client via the programmatic interface, respective second sets of completion parameters defining a second one or more unique completion states of execution of the application.

### Claim 9 (depends on 6)

The method of claim 6, wherein the application debugger is provided as part of an application development service of a provider network, wherein the provider network comprises a compute service, and wherein the plurality of execution runtimes are created using respective virtual machines of the compute service of the provider network.

### Claim 10 (depends on 6)

The method of claim 6, wherein the application debugger executes interactively on behalf of the client, and wherein the plurality of execution runtimes respectively execute non-interactively on behalf of the application debugger.

### Claim 11 (depends on 6)

The method of claim 6, wherein the plurality of execution runtimes are created using respective virtual machines provided by a non-interactive application debugging service of a provider network.

### Claim 12 (depends on 5)

The method of claim 5, wherein the execution coordinator executes non-interactively, wherein the plurality of initial states of execution of the application define a test case for a phase of a software testing life cycle; and wherein the one or more unique completion states of execution of the application comprise at least a passing completion state and a failing completion state.

### Claim 13

A non-transitory, computer-readable storage medium, storing program instructions that when executed on a computing device, causes the computing device to implement:
receiving, at an execution coordinator from a client via a programmatic interface, respective unique sets of application parameters defining a plurality of initial states of execution of an application;
creating a plurality of execution runtimes for the application corresponding to respective ones of the plurality of initial states, wherein the plurality of execution environments differ according to the respective unique sets of application parameters;
executing individual ones of the plurality of execution runtimes to termination according to one or more termination conditions; and
returning, by the execution coordinator to the client via the programmatic interface, respective sets of completion parameters defining one or more unique completion states of execution of the application.

### Claim 14 (depends on 13)

The non-transitory, computer-readable storage medium of claim 13, wherein the execution coordinator is an application debugger, wherein the sets of application parameters comprise respective sets of initialization values for different variables of the application, and wherein the one or more termination conditions comprise execution breakpoints.

### Claim 15 (depends on 14)

The non-transitory, computer-readable storage medium of claim 14, wherein a number of unique completion states of execution of the application is fewer than a number of unique initial states of execution of the application, and wherein the method further comprises:
analyzing the unique completion states of execution of the application to identify a portion of the unique initial states of execution of the application corresponding to the unique completion states of execution of the application; and
returning, by the execution coordinator to the client via the programmatic interface, the portion of the unique initial states of execution of the application.

### Claim 16 (depends on 15)

The non-transitory, computer-readable storage medium of claim 15, storing further instructions that when executed by the computing device, cause the computing device to further implement:
selecting respective additional unique sets of application parameters defining a second plurality of initial states of execution of an application according to the completion parameters defining the one or more unique completion states of execution of the application;
creating a second plurality of execution runtimes for the application corresponding to respective ones of the second plurality of initial states, wherein the second plurality of execution environments differ according to the respective additional unique sets of application parameters;
individually executing the second plurality of execution runtimes to termination according to one or more additional termination conditions; and
returning, by the execution coordinator to the client via the programmatic interface, respective second sets of completion parameters defining a second one or more unique completion states of execution of the application.

### Claim 17 (depends on 14)

The non-transitory, computer-readable storage medium of claim 14, wherein the application debugger is provided as part of an application development service of a provider network, wherein the provider network comprises a compute service, and wherein the plurality of execution runtimes are created using respective virtual machines of the compute service of the provider network.

### Claim 18 (depends on 14)

The non-transitory, computer-readable storage medium of claim 14, wherein the application debugger executes interactively on behalf of the client, and wherein the plurality of execution runtimes respectively execute non-interactively on behalf of the application debugger.

### Claim 19 (depends on 14)

The non-transitory, computer-readable storage medium of claim 14, wherein the plurality of execution runtimes are created using respective virtual machines provided by a non-interactive application debugging service of a provider network.

### Claim 20 (depends on 13)

The non-transitory, computer-readable storage medium of claim 13, wherein the execution coordinator executes non-interactively, wherein the plurality of initial states of execution of the application define a test case for a phase of a software testing life cycle; and wherein the one or more unique completion states of execution of the application comprise at least a passing completion state and a failing completion state.
