Open Source Linux Debuggers - Page 26

Expresses C program in graphical control flow chart in VCG GDL.

Displaying information about the contents of COFF format files which were built by CCS compiling tools of Texas Instruments; disassembling such COFF files.

chrome-remote-interface is a Node.js library that provides a convenient interface for interacting with the Chrome DevTools Protocol, allowing developers to control and instrument Chromium-based browsers programmatically. The project exposes browser debugging and automation capabilities through a straightforward JavaScript API that abstracts the underlying DevTools protocol commands and events. By connecting to a running browser instance with remote debugging enabled, developers can inspect network activity, manipulate pages, capture screenshots, automate navigation, and analyze performance metrics. The library is commonly used for building browser automation scripts, testing tools, web scraping systems, and custom developer tooling that interacts directly with Chrome internals. Unlike higher-level tools such as Puppeteer, Chrome Remote Interface focuses on exposing the raw protocol in a more flexible and transparent way.

cingb is an ATTEMPT to write a Gameboy-emulator for all kinds of platforms. It plays Gameboy and Gameboy Color ROMs, includes a debugger for step-by-step analysis of Gameboy programs and might be also interesting for educational purposes.

class.debug.php provide simple functions to set control infos in your code, with many options to output this info in your browser and/or write in a logfile - output of infos in browser, logfile or browser and logfile - (browser) output infos based on a error level - (browser) output infos compact or every message in a new line - (browser) output info based on a special pattern - (browser) output infos marked with special colors (html) - (logfile) log infos based on a error level - (logfile) log infos in a new file each execution, hour, day, week, month or year - (logfile) output infos compact or every message in a new line - (logfile) output info based on a special pattern TODO: - (logfile) create new logfiles based on a deadline - (logfile) create new logfiles based of a filesize - (logfile) create new logfiles based of a date - (logfile) create new logfiles based of a memorylimit look at debug_config to see all options

Codemon is a testing tool that enables code coverage of C codes. It supports the level of Decision Coverage and Condition Coverage.

dSpec is a BDD framework for Delphi/Pascal built as an extension of DUnit.

An ant task that applies -g debug labels to classes that don't have them. The line number attributes are synchronized to a decompiled asm source view of the classes. The tool generates both the modified 'src' and classes.

The dashx debugger is a program for tracing the execution of a target application. As code in the target is executed, the source code information is printed by dashx. The output includes the source file-name, line-number, and source line text.

dbfi (Debuggable Brainfuck interpreter) is a fast interpreter and brainfuck compiler (for x86). The interpreter allows you to debug your program with the character !, which print the value of the cells and your current position.

The dbg library is a set of C++ utilities to facilitate modern debugging idioms. It has been designed to support defensive programming techniques in modern C++ code. It integrates well with standard library usage and has been carefully designed to be e

The patch comm-manag allows ddd to start up correctly. Loads all the debug info files, Breakpoints are correct, project is correctly saved and loaded. ddd-3.3.12-260210 patch makes usable register display for MMX and SIMD instructions 32 - 64 bit.

A cross-platform implementation of a mutex, that automatically checks for everything, you might be doing wrong: - DeadLocks - Invalid mutex leave order - Thread Shutdown, while still holding mutex locks - Destroying a locked mutex - (Un)Locking a destroyed mutex - UnLocking an unlocked mutex - UnLocking an mutex locked by another thread - Locking a non-recursive, locked mutex - Not destroying all mutexes before application termination Every abnormal produces a console output with file and line information about were it is located and why it happened. The main purpose of debug_mutex is the detection of deadlocks and outputting useful information, to fix it, by telling you exactly, where the recursion happened. Debug_mutex can easily be disabled and simply used as a cross-platform mutex Library Debug_mutex can be linked statically or externally

This project is for homebrew console development tools based on the gnu compiler collection with additional tools and libraries to aid programming each supported console. The windows variants are built with MinGW.

DFhack is a library for cross-platform access to the memory of Dwarf Fortress.

a powerful disassembler for x86

Drow is an ELF linux analyzer coded in C.It is aimed to the low-level programmer. It is a console application which displays ELF file information in an human readable format, providing different options for different parts/aims of the file data.

FreePascal based debugger and freepascal debugger lib. An alternative for C-based gdb.

Function call tracing in the Linux kernel and userspace applications. Dynamically sets probes (using VProbes, a KProbes variant) and displays the function call trace of a process calling kernel or application functions. The superior of strace and ltrace.

Adapted from eclipse cde elf tools, enables java to generate dwarf symbols and register compiled method with gdb-jit interface. It is intended for JikesRVM/MRP to use, and currently has one provider interface.

ELFE will allow you to edit *nix binary files so far support only in linux / bsd systems the program uses ncurses and console based

elfviz is command line tool which parse and visualizes ARM-ELF(Executable and Linkable Format).

A NetBeans IDE Plugin for the Clojure Programming Language

erle - a development environment for erlang

Package errors provides simple error handling primitives. The traditional error handling idiom in Go that is applied recursively up the call stack results in error reports without context or debugging information. The errors package allows programmers to add context to the failure path in their code in a way that does not destroy the original value of the error. Wrap function returns a new error that adds context to the original error. Using errors.Wrap constructs a stack of errors, adding context to the preceding error. Depending on the nature of the error it may be necessary to reverse the operation of errors.Wrap to retrieve the original error for inspection. Any error value which implements this interface can be inspected by errors.Cause. errors.Cause will recursively retrieve the topmost error which does not implement causer, which is assumed to be the original cause.