Abstract: Interactive iterative program parallelization based on dynamic feedback program parallelization, in one aspect, may identify a ranked list of one or more candidate pieces of code each with one or more source refactorings that can be applied to parallelize the code, apply at least one of the one or more refactorings to create a revised code, and determine performance data associated with the revised code. The performance data may be used to make decisions on identifying next possible ranked list of refactorings.

Abstract: A debugger variable is set; the variable is associated with: at least one location within a program to be debugged; and at least one expression that is valid within a scope of the location. A breakpoint associated with a location within the program is also set. Upon encountering the at least one location of the debugger variable during a current run of the program, a value of the at least one expression with which the debugger variable is associated is computed and assigned to the debugger variable. Upon encountering the location of the breakpoint during the current run of the program, the debugger is operated in at least one of a first manner and a second manner, depending on the value of the debugger variable; the first manner is different than the second manner.

Abstract: A method of debugging a program includes setting a breakpoint in the program identifying a location within the program, a reference-typed expression that is valid within the scope of the location, and a set of statically-specified data entities to which the expression refers, upon encountering the location during a current run of the program, determining whether the associated expression evaluates to a reference corresponding to one of the statically-specified data entities, pausing the program at the location if a value of the expression refers to one of the statically-specified data entities, and continuing the program without pausing if the value does not refer to one of the statically-specified data entities.

Abstract: A method of debugging a program includes setting a breakpoint in the program identifying a location within the program, a reference-typed expression that is valid within the scope of the location, and a set of statically-specified data entities to which the expression refers, upon encountering the location during a current run of the program, determining whether the associated expression evaluates to a reference corresponding to one of the statically-specified data entities, pausing the program at the location if a value of the expression refers to one of the statically-specified data entities, and continuing the program without pausing if the value does not refer to one of the statically-specified data entities.

Abstract: Interactive iterative program parallelization based on dynamic feedback program parallelization, in one aspect, may identify a ranked list of one or more candidate pieces of code each with one or more source refactorings that can be applied to parallelize the code, apply at least one of the one or more refactorings to create a revised code, and determine performance data associated with the revised code. The performance data may be used to make decisions on identifying next possible ranked list of refactorings.

Abstract: A debugger provides a user interface for specifying filters of data structure data values. A programmer or the like specifies desired filters using the user interface. The debugger applies these filters to determine how to present program data, for example, at a breakpoint, or during a post-mortem inspection of program data.

Abstract: A debugger provides a user interface for specifying expansion rules for automatically expanding fields of data structure. A programmer or the like specifies desired expansion rules using the user interface. The debugger applies these expansion rules to determine how to present program data, for example, at a breakpoint, or during a postmortem inspection of program data.

Abstract: A software module for searching within a software debugging environment is provided. The software module comprises a search component and an interface component. The search component is configured to be implemented within a debugging tool configured to access a set of execution state data for a program being monitored by the debugging tool when execution of the program is stopped. The search component is configured to search the set of execution state data to locate instances of a particular value. The interface component is configured to allow a user to specify the particular value in a search query, submit the search query to the search component, and present a description of each instance of the particular value located by the search component to the user.