Projects tagged ‘profiler’ and ‘tracer’

trace-cmd provides a convenient interface to the ftrace tracing mechanism in the Linux kernel. It can run a command with various tracing options enabled, and then generate a report of the tracing results.

Lets you see your Python program's execution as a tree of function invocations, each tree node exposing the real time, and CPU time (user/sys) of that call. This project consists of two main ... [More] components: A Python tracer that can run your Python programs (much like "cProfile" and friends). A Gtk+ based GUI that can show the trace results. It uses a tiny auxiliary library written for it "graphfile" to allow append-only writing and reading static DAG's directly from file without reading it whole into memory at any stage. [Less]

.NET WinForm application for profiling SQL queries. You can execute stored procedures and see the result and also open and edit stored procedures on the fly

IntroductionThe Debug-JS project is designed to provide an easy, clean and clear way to debug JavaScript applications. This is a minimal-powerful implementation that's provides a set of debugging ... [More] , tracing and profiling tools designed using AOP. Debug-JS is easy. Why? It's object-oriented. It attaches to any object without adding dirty code into the application. It's compatible with several JS frameworks (see Compatibility page). It doesn't requires complex code implementation in order to be used. It's cross-browser compatible. Debug-JS is useful. Why? It has debugging, tracing and profiling support. It causes no overhead because uses only standard JavaScript. It could be used in any browser. It's lightweight, < 5KB packed and < 20KB the development version. It works all over a plugin architecture to extend and modify Debug-JS as needed. Good news!Now, you can use Maven to build Debug-JS! Using Maven is easier to make changes, create test cases and even new releases. You need to checkout the project first, from the following url: svn checkout http://debug-js.googlecode.com/svn/trunk/ debug-js-read-only And next you can use Maven in the project root directory: mvn clean install It will make a distribution including a site which allows to test Debug-JS in action. For more information, please see Setting up a Maven Environment in the wiki. Current ReleaseDebug-JS 0.11a (Galadriel) is ready for download!. For information about features in this version, please see the Release Notes How it works?Basic Debug-JS usage could be in three steps: 1. You should add the Debugger.js file to your HTML and initialize the framework. /* Include */ // Yes... it could be unattended, but you're free to choose :) Debugger.setup(); 2. You should create a Wrapper object and set the event handlers. /** * This handler will be called if any error occurs * inside the object that's being debugged. * * @param event {Debugger.DebugEvent} Event data. */ function errorHandler(event) { alert("Oops!, you became exceptional: " + event.data.error.message ); } var wrapper = new Debugger.Wrapper(errorHandler);3. You just need to attach the debugger to an object. var myObject = { foo : function() { // Error: Object 'bar' is undefined. alert(this.bar.foo); } }; myObject.debug(wrapper); myObject.foo(); // This call will throw an error.Now, every time that myObject throws an error in one of its methods (for example, when executes foo method), the errorHandler function will be notified. For information about different kind of handlers (tracing handler, profiling handler) please see the documentation. [Less]