Projects tagged ‘debug’ and ‘debugging’

xLog is a PHP extension that allows extended logging of PHP errors, including Fatal errors. Output typically includes referral, GET values, URL, and a full backtrace. Additional information can be ... [More] included via custom variables by the developer at runtime. [Less]

Reverse engineering suite. This project will include a disassembler (modeled after IDA) and a number of other tools associated with reverse engineering.

Protoeditor is a small KDE text editor developed for debugging scripts interactively. The goal is to provide a simple editor supporting a variety of debuggers for different languages.

The WinAppDbg python module allows developers to quickly code instrumentation scripts in Python under a Windows environment. It uses ctypes to wrap many Win32 API calls related to debugging, and ... [More] provides an object-oriented abstraction layer to manipulate threads, libraries and processes, attach your script as a debugger, trace execution, hook API calls, handle events in your debugee and set breakpoints of different kinds (code, hardware and memory). Additionally it has no native code at all, making it easier to maintain or modify than other debuggers on Windows. [Less]

Library to debug STL containers, specially useful from GDB. This project belongs to FuDePAN. IntroductionThis library helps to debug C++ applications that use STL. It's specially tuned to overcome ... [More] the issues that GDB has as of version 6.8. Basically, the library provides functions to inspect and display STL containers. UsageThree functions are provided: stl_element(container, id) that retrieves an element address from a container based on the id. The id type depends on the container type. stl_print() and it's overloaded flavors: stl_print(container) that dumps the container content. stl_print(iterator) shows the element being iterated. stl_print(used-defined-type) shows a user-defined type (if stl_to_cout was provided for such type, see below). stl_size(container) that retrieves the number of elements of the container. In order to use stl_debug, follow these steps: #include stl_debug.h in every file containing STL containers you will want to debug. #include stl_debug_impl.h once in some .cpp/.cc source file teach the library what containers (with what types) you will want to dump/access, registering the containers by using the STL_DEBUG_REGISTER_* macros (see below). define the STL_DEBUG_ENABLE macro, i.e. by addding -DSTL_DEBUG_ENABLE command line flag to g++ of course, build with -g or -ggdb Registering the containers to debugEach STL container template instantiation that needs to be debugged has to be registered. For example, vector needs to be registered. In order to register the containers, call the registration macros in the file where the stl_debug_impl.h file was included, out of any function (at file level). There is a registration type macro for each container type. The registration macros so far are: STL_DEBUG_REGISTER_VECTOR(type) enables debugging of std::vector. STL_DEBUG_REGISTER_LIST(type) enables debugging of std::list. STL_DEBUG_REGISTER_SET(type) enables debugging of std::set. STL_DEBUG_REGISTER_MAP(key,type) enables debugging of std::map. If the type is a symbol declared in the private or protected part of a class, redeclare it with STL_DEBUG_PRIVATE or STL_DEBUG_PROTECTED macros, that replace private and protected respectively. When the library is disabled (i.e. STL_DEBUG_ENABLE is undefined), these macros expand to the proper public/protected access modifiers. Using the debugging functionsRefer to the example for precise instructions. The id parameter of stl_element() function depends on the container type: the index for std::vector the key for std::map FIRST_ELEMENT or LAST_ELEMENT for both vector and lists. stl_element is not available for sets. Accessing members of a map with string keySuppose you have a map from strings to type T: std::map, and you need to access a memeber mapped with key "hello". Since gdb will not call the string constructor from the c-string "hello", you have to call stl_to_str("hello") to create the key: print *stl_element(mymap, stl_to_str("hello"))stl_element returns the pointer to the element. Such pointer can be either modified or just printed. Dumping containers containing user-defined typesIn order to dump containers that contain user-defined types, you have to provide a dumping function for those types. To define the dumping function, use the DECLARE_STL_TO_COUT(type) macro to declare the heading of the function, then invoke stl_print() to print the individual attributes of your type. The parameter can be accessed as p: #ifdef STL_DEBUG_ENABLE DECLARE_STL_TO_COUT(MyClass::MyStruct) { /* 'p' is the parameter */ stl_print(p.a, false); stl_print(" ", false); stl_print(p.b, false); } #endifPass 'false' as the second argument of stl_print to avoid generating a new line. See example.cpp for a complete example. Printing a specific element of a containerTo print a specific element, use stl_print combined with stl_element. call stl_print(*stl_element(myvec, 10)) call stl_print(*stl_element(mymap, stl_to_str("hello")))It will work for standard types; for used-defined types, see section above. Keeping your code cleanIn order to keep your code 'clean' (not messing it with debugging code), I suggest you to create a debug_support.h file where you put in there all the stl-debug related code (i.e. STL_DEBUG_REGISTER_xxx and DECLARE_STL_TO_COUT macros calls, etc.), so the only things you have to add to your main code, are the includes, and the STL_DEBUG_PRIVATE/PROTECTEDs. Include your debug_support.h file after all your class definitions. Coming soonSupport for multimaps and multisets will follow. [Less]

A runtime debugging and scripting tool that gives you access to the internals of a WPF or Windows Forms application

ODbgExt is an open source debugger extension for WinDbg that is intended to be developed by the debugging community. It is based on the Windows Debugger SDK Sample ‘exts’ and uses the COM Debugger ... [More] interface IDebugControl. The primary objective of the project is to provide the debugging community a central location to share their debugger extensions that help to isolate common problems in the community and make debugging both live systems and dumps easier. The initial release will be the basic framework that we expect other developers to contribute to. There will be very basic functionality in the initial version. We, GES (Global Escalation Services) intend on doing a series of blogs to talk about writing debugger extensions over the coming year. As we blog about writing extension we will include the code in ODbgExt (This project). This is the same group that runs the http://blogs.msdn.com/ntdebugging blog. We encourage you to sign up and contribute your debugger extension ideas and or code to the project. Simply create a codeplex account and request access. For more details see the discussions section for ideas! [Less]

Utility classes, JSP tags, Servlets, and extensions to different external API. IntroductionDebuggingFilter is a servlet filter that add a "debug.jspInfo" attribute to the current request to be used ... [More] in jsp pages, for debugging purpose. SamplesSee how the debug info will look like. ConfigurationConfigure web.xmlAdd this to your WEB-INF/web.xml file: debugging ro.raisercostin.web.DebuggingFilter debugging /* Configure web.xmlAdd this to desired jsp file : ${debug.jspInfo}Configure loggingTo log the request parametes add in log4j.properties file : log4j.logger.ro.raisercostin.web.DebuggingFilter.PARAMETERS=debugTo log the request and header parameters add in log4j.properties file : log4j.logger.ro.raisercostin.web.DebuggingFilter.REQUEST=debugTo log all environment parameters add in log4j.properties file : log4j.logger.ro.raisercostin.web.DebuggingFilter.ALL=debugConfigure maven dependenciesAdd this to your pom.xml file, inside /project/dependencies/ : ro.raisercostin raisercostin-jsp 1.0 Add this to your pom.xml file, inside /project/repositories/ : raisercostin raisercostin http://raisercostin.googlecode.com/svn/maven2 [Less]

Tired of debugging Python using print statements? Don't like the cumbersome PDB (Python debugger) console? Prefer using Vim for coding your Python programs? VimPdb is the solution - allows debugging ... [More] Python in an IDE-fashion, right within the Vim editor. Features:Highlighting of currently debugged line and breakpoint lines. F5 - Run/continue running. F2 - Toggle breakpoint at current line Ctrl-F2 / Shift-F2 - Toggle conditional/temporary breakpoint. F7 / F8 - Step into/over F12 - Print stack trace F3 / Ctrl-F3 - Eval/Exec a given statement (in the current debugging context) Save/load breakpoints into session files. Cross-platform And many more... See readme.txt for details Download and InstallClick here to download the sources. Just drop vimpdb.py and vimpdb.vim into your Vim plugin directory, and you're all set to go. Important NotesIt's still considered Beta, so I'm not too sure about its stability or lack of bugs. However, I do appreciate if you could report bugs, suggest features or help out with the known issues (see "Known Issues" section in readme.txt). Email me at vimpdb@gmail.com It's possible to easily implement the debugging capabilities for another editor (e.g. Emacs) - you could write a Python class of your own, which inherits from the PdbIDE class, and implements editor-specific functionalities (such as highlighting). [Less]

Using PowerShell, you interact with .NET objects during debugging in the Visual Studio IDE. The PowerShell Visualizer injects objects, presents a scripting window. And more.... Decorate your classes ... [More] like so: [DebuggerVisualizer(typeof(PoSHVisualizer.PoSHVisualizer))] [Serializable] Hit a breakpoint, launch a PowerShell session and operate on that object. Create a custom visualizer by inheriting from the PoSHVisualizer. Inject variables you want into the PowerShell environment. [Less]