Abstract: A computer-implemented method includes generating static analysis data by performing static analysis on a program. A breakpoint is set in the program automatically, by a computer processor, based on the static analysis data. The breakpoint is hit during a runtime of the program. A program bug is automatically identified at a context location of the breakpoint when the breakpoint is hit during the runtime of the program. An interactive debugging session of the program is launched automatically at the context location of the breakpoint, based on the identifying the program bug.

Abstract: A computer-implemented method includes generating static analysis data by performing static analysis on a program. A breakpoint is set in the program automatically, by a computer processor, based on the static analysis data. The breakpoint is hit during a runtime of the program. A program bug is automatically identified at a context location of the breakpoint when the breakpoint is hit during the runtime of the program. An interactive debugging session of the program is launched automatically at the context location of the breakpoint, based on the identifying the program bug.

Abstract: Examples of techniques for setting a stack pattern breakpoint for a COBOL program are disclosed. In one example implementation according to aspects of the present disclosure, a computer-implemented method may include providing a static program control flow view of a plurality of COBOL paragraphs of the COBOL program. The method may further include enabling a user to select the stack pattern using the static program control flow view of the plurality of COBOL paragraphs of the COBOL program. The method may also include setting, by a processing device, the stack pattern breakpoint in source code of the COBOL program using information from a compiler compiling the COBOL program to create a pseudo-stack that can be operated on by a debugger to evaluate stack pattern conditions for the plurality of COBOL paragraphs.

Abstract: According to embodiments of the present invention, machines, systems, methods and computer program products for controlling two or more remote sessions are provided. Two or more remote sessions are synchronized to control each session using a common interface. One or more executable commands are sent to each remote session at substantially the same time using the common interface to control operation of that remote session. Data generated by each remote session from executing the commands is received and analyzed to identify one or more differences in data generated by each remote session. The one or more identified differences in the data are displayed on the common interface. An indication may be provided regarding possible root causes of the differences in the data generated by each remote session. Each remote session includes a program debug session. A report comprising the one or more identified differences in the data may be generated.

Abstract: Examples of techniques for setting a stack pattern breakpoint for a COBOL program are disclosed. In one example implementation according to aspects of the present disclosure, a computer-implemented method may include providing a static program control flow view of a plurality of COBOL paragraphs of the COBOL program. The method may further include enabling a user to select the stack pattern using the static program control flow view of the plurality of COBOL paragraphs of the COBOL program. The method may also include setting, by a processing device, the stack pattern breakpoint in source code of the COBOL program using information from a compiler compiling the COBOL program to create a pseudo-stack that can be operated on by a debugger to evaluate stack pattern conditions for the plurality of COBOL paragraphs.

Abstract: Examples of techniques for setting a stack pattern breakpoint for a COBOL program are disclosed. In one example implementation according to aspects of the present disclosure, a computer-implemented method may include providing a static program control flow view of a plurality of COBOL paragraphs of the COBOL program. The method may further include enabling a user to select the stack pattern using the static program control flow view of the plurality of COBOL paragraphs of the COBOL program. The method may also include setting, by a processing device, the stack pattern breakpoint in source code of the COBOL program using information from a compiler compiling the COBOL program to create a pseudo-stack that can be operated on by a debugger to evaluate stack pattern conditions for the plurality of COBOL paragraphs.

Abstract: Examples of techniques for setting a stack pattern breakpoint for a COBOL program are disclosed. In one example implementation according to aspects of the present disclosure, a computer-implemented method may include providing a static program control flow view of a plurality of COBOL paragraphs of the COBOL program. The method may further include enabling a user to select the stack pattern using the static program control flow view of the plurality of COBOL paragraphs of the COBOL program. The method may also include setting, by a processing device, the stack pattern breakpoint in source code of the COBOL program using information from a compiler compiling the COBOL program to create a pseudo-stack that can be operated on by a debugger to evaluate stack pattern conditions for the plurality of COBOL paragraphs.

Abstract: Examples of techniques for setting a stack pattern breakpoint for a COBOL program are disclosed. In one example implementation according to aspects of the present disclosure, a computer-implemented method may include providing a static program control flow view of a plurality of COBOL paragraphs of the COBOL program. The method may further include enabling a user to select the stack pattern using the static program control flow view of the plurality of COBOL paragraphs of the COBOL program. The method may also include setting, by a processing device, the stack pattern breakpoint in source code of the COBOL program using information from a compiler compiling the COBOL program to create a pseudo-stack that can be operated on by a debugger to evaluate stack pattern conditions for the plurality of COBOL paragraphs.

Abstract: Examples of techniques for setting a stack pattern breakpoint for a COBOL program are disclosed. In one example implementation according to aspects of the present disclosure, a computer-implemented method may include providing a static program control flow view of a plurality of COBOL paragraphs of the COBOL program. The method may further include enabling a user to select the stack pattern using the static program control flow view of the plurality of COBOL paragraphs of the COBOL program. The method may also include setting, by a processing device, the stack pattern breakpoint in source code of the COBOL program using information from a compiler compiling the COBOL program to create a pseudo-stack that can be operated on by a debugger to evaluate stack pattern conditions for the plurality of COBOL paragraphs.

Abstract: Without using a high-level programming language source code, a set of sync points is identified in an initial binary code. The initial binary code is executed at a first system. A value of the user data is captured from a user space of a memory as a baseline of the user data. A set of comparative sync points is identified in a second binary code. During an execution of the second binary code, a second value of the user data from a second user space of a second memory is found to fail in matching the baseline of the user data. An instruction before the comparative sync point in the second binary code is identified as a location of a faulty operation due to the failing.

Abstract: According to embodiments of the present invention, machines, systems, methods and computer program products for controlling two or more remote sessions are provided. Two or more remote sessions are synchronized to control each session using a common interface. One or more executable commands are sent to each remote session at substantially the same time using the common interface to control operation of that remote session. Data generated by each remote session from executing the commands is received and analyzed to identify one or more differences in data generated by each remote session. The one or more identified differences in the data are displayed on the common interface. An indication may be provided regarding possible root causes of the differences in the data generated by each remote session. Each remote session includes a program debug session. A report comprising the one or more identified differences in the data may be generated.

Abstract: Breakpoints are handled in an asynchronous debug model by building a queue of basic operations to run a debug application program interface (API). User commands are each broken down into a simple command and placed on the queue. In response to a debug event, a new simple command is generated. If, when a first command on the queue is processed, a thread is not stopped at a location with an installed breakpoint, an operation corresponding to the first command is started, the operation is removed from the queue, and a next operation is started. If the thread is stopped at the location with the breakpoint, the thread performs a hop. When the hop terminates, the first command is removed from the queue. If the first command is a run command, and there is no cause to stop the thread, the run command is moved to the end of the queue.

Abstract: Breakpoints are handled in an asynchronous debug model by building a queue of basic operations to run a debug application program interface (API). User commands are each broken down into a simple command and placed on the queue. In response to a debug event, a new simple command is generated. If, when a first command on the queue is processed, a thread is not stopped at a location with an installed breakpoint, an operation corresponding to the first command is started, the operation is removed from the queue, and a next operation is started. If the thread is stopped at the location with the breakpoint, the thread performs a hop. When the hop terminates, the first command is removed from the queue. If the first command is a run command, and there is no cause to stop the thread, the run command is moved to the end of the queue.

Abstract: Breakpoints are handled in an asynchronous debug model by building a queue of basic operations to run a debug application program interface (API). User commands are each broken down into a simple command and placed on the queue. In response to a debug event, a new simple command is generated. If, when a first command on the queue is processed, a thread is not stopped at a location with an installed breakpoint, an operation corresponding to the first command is started, the operation is removed from the queue, and a next operation is started. If the thread is stopped at the location with the breakpoint, the thread performs a hop. When the hop terminates, the first command is removed from the queue. If the first command is a run command, and there is no cause to stop the thread, the run command is moved to the end of the queue.

Abstract: Breakpoints are handled in an asynchronous debug model by building a queue of basic operations to run a debug application program interface (API). User commands are each broken down into a simple command and placed on the queue. In response to a debug event, a new simple command is generated. If, when a first command on the queue is processed, a thread is not stopped at a location with an installed breakpoint, an operation corresponding to the first command is started, the operation is removed from the queue, and a next operation is started. If the thread is stopped at the location with the breakpoint, the thread performs a hop. When the hop terminates, the first command is removed from the queue. If the first command is a run command, and there is no cause to stop the thread, the run command is moved to the end of the queue.