Abstract: Method and apparatus for enhancing an executable is disclosed herein. In one embodiment, the method includes instrumenting an executable with additional program code to detect run-time errors, and while running the instrumented executable within a debug environment generating the run-time errors detected by the additional program code, upon reaching a breakpoint, identifying any of the run-time errors which occurred while executing a function in which the breakpoint is located, and transmitting an indication of the identified run-time errors to the debugging environment.

Abstract: Method and apparatus for enhancing an executable is disclosed herein. In one embodiment, the method includes instrumenting an executable with additional program code to detect run-time errors, and while running the instrumented executable within a debug environment generating the run-time errors detected by the additional program code, upon reaching a breakpoint, identifying any of the run-time errors which occurred while executing a function in which the breakpoint is located, and transmitting an indication of the identified run-time errors to the debugging environment.

Abstract: A tool with an electrical circuit to provide indications whether the tool is properly engaged with a fastener or other workpiece is provided. The tool includes a handle and an end effector configured to engage the fastener or workpiece. The end effector includes sensors arranged on surfaces of the end effector that contact the fastener or workpiece when the end effector is properly engaged with the fastener or workpiece. The sensors are electrically connected to an indicator via an electrical circuit. The electrical circuit causes the indicator to output different indications depending on whether none, some, or all of the sensors are in contact.

Abstract: The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, the IDE receives a request to add an assertion at a specified location within source code of an application from a user interacting with an integrated development environment (IDE) tool. The source code is stored in a first file associated with a development project. The IDE tool receives a definition for the assertion and stores the definition for the assertion in a second file associated with the development project. The IDE tool creates an association in the development project between the source code of the application and the assertion.

Abstract: The present disclosure relates to maintaining assertions in source code components of a development project by an integrated development environment (IDE) tool. According to one embodiment, a request is received to build a software application generated from the development project. Based on prior executions of the software application, resource requirements for each of one or more assertions included in the prior executions of the software application are identified. One or more of the assertions based on the identified resource requirements are selectively inserted in the source code components. The source code components of the development project are compiled to build the software application.

Abstract: The present disclosure relates to maintaining assertions in source code components of a development project by an integrated development environment (IDE) tool. According to one embodiment, a request is received to build a software application generated from the development project. Based on prior executions of the software application, resource requirements for each of one or more assertions included in the prior executions of the software application are identified. One or more of the assertions based on the identified resource requirements are selectively inserted in the source code components. The source code components of the development project are compiled to build the software application.

Abstract: The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, the IDE receives a request to add an assertion at a specified location within source code of an application from a user interacting with an integrated development environment (IDE) tool. The source code is stored in a first file associated with a development project. The IDE tool receives a definition for the assertion and stores the definition for the assertion in a second file associated with the development project. The IDE tool creates an association in the development project between the source code of the application and the assertion.

Abstract: The present disclosure relates to managing assertions in program source code in an integrated development environment (IDE) tool. According to one embodiment, the IDE tool receives a request to execute an application built from source code of a development project from a user interacting with an integrated development environment (IDE) tool. The IDE tool identifies changes to one or more of the source code of the development project from a previous version of the one or more source code. Based on the changes to the source code, the IDE tool selectively identifies one or more assertions to insert in the source code based on the identified changes.

Abstract: The present disclosure relates to managing assertions in program source code in an integrated development environment (IDE) tool. According to one embodiment, the IDE tool receives a request to execute an application built from source code of a development project from a user interacting with an integrated development environment (IDE) tool. The IDE tool identifies changes to one or more of the source code of the development project from a previous version of the one or more source code. Based on the changes to the source code, the IDE tool selectively identifies one or more assertions to insert in the source code based on the identified changes.

Abstract: The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, while the IDE tool is compiling the source code of a development project, the IDE tool generates at least a first compiler warning. The first compiler warning generally corresponds to at least one line of source code in a first source code component of the development project. A first set of assertions to add to the source code of the development project is determined based on the line of source code that resulted in the first compiler warning. The IDE tool adds the first set of assertions to the source code of the development project. The first set of assertions are compiled as part of the source code of the development project.

Abstract: The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, while the IDE tool is compiling the source code of a development project, the IDE tool generates at least a first compiler warning. The first compiler warning generally corresponds to at least one line of source code in a first source code component of the development project. A first set of assertions to add to the source code of the development project is determined based on the line of source code that resulted in the first compiler warning. The IDE tool adds the first set of assertions to the source code of the development project. The first set of assertions are compiled as part of the source code of the development project.

Abstract: Disclosed aspects include identifying basic blocks of a program. For each basic block, the compiler inserts an identifier that includes the function name, and is coupled with a counter variable. In response to generating the identifier coupled with the counter variable, the program is compiled. During program execution, the counter value is incremented in response to a call of the basic block when executing the program. In response to incrementing the counter value, the counter value coupled with the identifier is displayed.

Abstract: Systems, methods, and computer program products to discover weak consistency errors in an application, by executing, by a debugger, a first thread of the application, by, determining that a first instruction in the first thread specifies to store a first value at a first memory address, setting a current value stored in the first memory address as an old value for the first memory address in a container for the first thread, executing the first instruction to store the first value at the first memory address, and setting the first value as a new value for the first memory address in the container for the first thread. The debugger then executes a second thread of the application, by restoring old values in the containers for all other threads and restoring a new value for each memory address specified in a container for the second thread to its respective memory address.

Abstract: Disclosed aspects include identifying basic blocks of a program. For each basic block, the compiler inserts an identifier that includes the function name, and is coupled with a counter variable. In response to generating the identifier coupled with the counter variable, the program is compiled. During program execution, the counter value is incremented in response to a call of the basic block when executing the program. In response to incrementing the counter value, the counter value coupled with the identifier is displayed.

Abstract: Methods to discover weak consistency errors in an application, by executing, by a debugger, a first thread of the application, by, determining that a first instruction in the first thread specifies to store a first value at a first memory address, setting a current value stored in the first memory address as an old value for the first memory address in a container for the first thread, executing the first instruction to store the first value at the first memory address, and setting the first value as a new value for the first memory address in the container for the first thread. The debugger then executes a second thread of the application, by restoring old values in the containers for all other threads and restoring a new value for each memory address specified in a container for the second thread to its respective memory address.

Abstract: Method and apparatus for enhancing an executable is disclosed herein. In one embodiment, the method includes instrumenting an executable with additional program code to detect run-time errors, and while running the instrumented executable within a debug environment generating the run-time errors detected by the additional program code, upon reaching a breakpoint, identifying any of the run-time errors which occurred while executing a function in which the breakpoint is located, and transmitting an indication of the identified run-time errors to the debugging environment.

Abstract: Method and apparatus for enhancing an executable is disclosed herein. In one embodiment, the method includes instrumenting an executable with additional program code to detect run-time errors, and while running the instrumented executable within a debug environment generating the run-time errors detected by the additional program code, upon reaching a breakpoint, identifying any of the run-time errors which occurred while executing a function in which the breakpoint is located, and transmitting an indication of the identified run-time errors to the debugging environment.

Abstract: Disclosed aspects include identifying basic blocks of a program. For each basic block, the compiler inserts an identifier that includes the function name, and is coupled with a counter variable. In response to generating the identifier coupled with the counter variable, the program is compiled. During program execution, the counter value is incremented in response to a call of the basic block when executing the program. In response to incrementing the counter value, the counter value coupled with the identifier is displayed.

Abstract: Disclosed aspects include identifying basic blocks of a program. For each basic block, the compiler inserts an identifier that includes the function name, and is coupled with a counter variable. In response to generating the identifier coupled with the counter variable, the program is compiled. During program execution, the counter value is incremented in response to a call of the basic block when executing the program. In response to incrementing the counter value, the counter value coupled with the identifier is displayed.

Abstract: Disclosed aspects include a debugger evaluating an expression. The expression has a debug element. Using dynamic analysis, a set of state information related to the debug element is identified. The set of state information can be generated external to the debugger and used within the debugger subsequent to being generated. Utilizing the set of state information, a tolerance parameter is selected. The tolerance parameter is for a conditional breakpoint linked with the debug element. In response to selecting the tolerance parameter, a triggering event for the conditional breakpoint may be detected. Based on the tolerance parameter, it may be determined to disregard the triggering event. Subsequently, the triggering event can be disregarded. Altogether, aspects of the disclosure provide a methodology for debug management that may provide performance or efficiency benefits.