Search Results for "developer ide source"

Developer tool for automatic runtime tracing software errors with various resources. Number of resources virtually unlimited.

Libinstrument is a complete and easy way to do custom function instrumentation for C/C++. The project comes ready with classic applications of instrumentation, such as AOP (Aspect Oriented Programming), Concern and Side Effect injection, stack tracing, exception tracing, basic time profiling, callgraph profiling and other. A GC (Garbage Collector) module is also under development. Libinstrument is highly portable and decoupled. The project comes with a CMake build system, integration with...

ParTools allows the interactive analysis of a C program execution profile and data dependencies to facilitate the discovery and selection of suitable parallelization candidates in a manual parallelization process. The flow does not assume any specific parallelization technique, thus it can be broadly applied. The original (serial) C source is automatically annotated to trace the execution profile and data dependencies at run-time. The annotated program is then executed using a significant (but small) data set selected by the developer. The data collected is cross-referenced with the original source and can be interactively analyzed graphically to determine the best parallelization candidates and techniques.

...Also, it was not possible to install a development environment onto the production machines, so the only solution was to develop a debugger which didn't need any user/developer interaction. I used many open source resources, then I decided to make the Bug Finder an open source project. It is built over a pluggable architecture to support other languages different from Borland Delphi (the one I used to develop my faulting application and the Bug Finder too). Here is the article http://www.codeproject.com/Articles/602794/Bug-Finder-a-real-Win32-extensible-passive-debugge .

Foo Test is a small, fast C-function unit testing project. It is capable of both benchmarking and validating C-functions while writing most of the test code through an easy perl script, and all the developer needed code can be added to a single file.