Abstract: A dynamic instrumentation system is described herein that performs dynamic, in-memory software code instrumentation achieved by injecting a library into the process to intercept module loads and instrument the methods in those modules with appropriate probes. The system instruments original methods to redirect execution to new methods to perform code verification tasks. By performing dynamic instrumentation, no binaries are modified on-disk, any existing code signing is preserved, and the locations from which the binaries are loaded do not matter. The system allows instrumentation to occur on any computing device, without pre-preparation by a tester or developer to install instrumented binaries. The system also does not involve gaining access to potentially sensitive locations on disk, as the binaries are modified in memory with the originals still unchanged on disk. Thus, the dynamic instrumentation system allows for more effective code analysis with less preparation and hassle for code developers.

Abstract: Various technologies and techniques are disclosed for facilitating a feedback process regarding the impact that changes to source code will have on tests. Changes contained in at least one source code file are analyzed in combination with code coverage information contained in a data store for a plurality of tests to determine when any of the tests will be impacted by the changes. When at least one test is determined to be impacted by the changes made to the source code file, a warning notification is displayed to a user to notify the user of a possible impact of the changes on the at least one test.

Abstract: Custom build tools are integrated into a design environment build process without writing code. Properties of the tool are defined in a file describing the appropriate syntax of the tool's command line. Values are specified for a particular use of the tool in a particular project. At runtime the command line for the tool is generated from the generalized syntax as defined in the file and the stored values.

Abstract: Various technologies and techniques are disclosed for facilitating a feedback process regarding the impact that changes to source code will have on tests. Changes contained in at least one source code file are analyzed in combination with code coverage information contained in a data store for a plurality of tests to determine when any of the tests will be impacted by the changes. When at least one test is determined to be impacted by the changes made to the source code file, a warning notification is displayed to a user to notify the user of a possible impact of the changes on the at least one test.