Open Source Linux Debuggers - Page 21

The Log & Dbug Library is an open source PL/SQL library, useful to log/debug your programs in the development phase and trace their activity and performances in production. It is ideal to improve your efficiency and code quality.

Simple 100% native plsql logger

Find us at https://github.com/powertechpreview/powertechpreview

Postscript IDE for Eclipse

Parallelized GDB: a tool for debugging parallel programs written in MPICH. Written in C++ and on the brink (hopefully) of usability. Please help develop!

Performance profiler is designed to profile single and multi-threading software.

A Curses-based Perl debugger with most of the essential functions such as monitoring windows for paddlist, call stack, custom watch expressions, etc. Suitable for debugging or tracing complicated Perl applications on the spot.

pastebin is here to help you collaborate on debugging code snippets. If you're not familiar with the idea, most people use it like this: submit a code fragment to pastebin, getting a url like hxxp://yoursite.com/1234, paste the url into an IRC or IM conversation, someone responds by reading and perhaps submitting a modification of your code, you then view the modification, maybe using the built in diff tool to help locate the changes

Log any javascript or php variables and it's back stack into file like php function debug_backtrace done. View the variables value and it's back stack info in web browser, and browser will synchronize with the log file using ajax.

Piet++ is the foremost interpreter for Piet++, an extension and expansion over the original Piet programming language.

PlugProxy version is a port forwarder/port debugger written in Java. PlugProxy is used to forward data from one TCP port to another. This is commonly referred to as "port forwarding." The purpose of this is to invisibly send a request from one site

Printr Debugger is an Actionscript implementation of the "print_r" function from PHP. It has a lot of options, the results are presented in the Output Window or in the Printr Debugger Flash Panel. It offers remote inspection too.

System monitoring utility, written in plain C. Allows application execution and performance monitoring, saving results into XML files. Monitors CPU, memory, network and disk usage on a per-application or per-system basis.

Proctor is a tool for running unit tests for Python programs. It uses the standard unittest module, and provides a GUI and command line interface for finding and running all tests available in a package or set of packages.

Prolint is a tool for automated source code review of Progress 4GL code. Prolint can enforce company coding standards and finds sloppy code and code that may perform differently than how the programmer intended.

Proshee is a Prolog type-inference system written in Prolog but depending on the banshee project in C (banshee.sourceforge.net). At present it manages very simple type-inference, but it has some problems with lists that need to be overcome.

It’s easy to make great things in PHP, but bugs can creep in just as easily. Psalm is a free & open-source static analysis tool that helps you identify problems in your code, so you can sleep a little better. Psalm helps people maintain a wide variety of codebases, large and small, ancient and modern. On its strictest setting it can help you prevent almost all type-related runtime errors, and enables you to take advantage of safe coding patterns popular in other languages. Psalm also fixes bugs automatically, allowing you to improve your code without breaking a sweat. If Psalm cannot infer a type for an expression then it uses a mixed placeholder type. mixed types can sometimes mask bugs, so keeping track of them helps you avoid a number of common pitfalls. Psalm has a Language Server that’s compatible with a range of different IDEs. Psalm can fix many of the issues it finds automatically.

This is a Linux command line utility to preprocess, tokenize, and "burn" PBasic source files to Parallax Inc.'s Basic Stamp II series of Microprocessors.

Usually, coding a script involves writing the code and either debugging or running it several times, examining variables or output and fixing the code until the desired effect is achieved. With PyCodebug, you get to see the effects of the code during coding, which greatly reduces the time needed to write a script. ================================== Demo Video: http://youtu.be/a6nFo4y3kzo ================================== Requires: Python 2.7x PySide

PySnooper is a simple yet powerful Python debugging utility. Just add a @pysnooper.snoop() decorator, and it logs line-by-line execution with timestamps and local variable tracking—saving you from inserting print() statements manually.

pyringe is a powerful Python process “syringe” that attaches to a running interpreter and lets you introspect—and even execute code inside—that live process. It blends debugger-style attachment (via gdb/ptrace techniques) with Python-aware helpers so you can inspect threads, frames, locals, and heap objects without restarting the target. This is invaluable for post-mortem diagnosis of production daemons where reproducing a bug in a dev shell is impractical. pyringe can inject arbitrary Python into the target process, enabling on-the-spot logging, state dumps, or gentle patching to keep a system limping along while you gather evidence. It’s also useful for forensic snapshots: enumerate objects of a certain type, find reference cycles, or measure memory pressure without pre-instrumentation. While powerful, it’s designed for careful, auditable use—showing exactly what code runs and where—so teams can regain visibility when black-box processes go sideways.

This module goal is to make the debugging tool of python shell even better. By replacing a few methods in the sys module. Standard error traceback are more powerfull with bettererror.py.

QDisassembler Interactive Disassembler

QUASI is stand-alone AVR RISC processor simulator with debugging features, EDA-like GUI and plugin interface.

Quercitools has just one tool for now - stackcheck.py. It helps in troubleshooting of stack overruns. Such defects destroy stack contents and locating the source of the problem is not easy. This is where stackcheck.py comes to help. It runs a program under test by gdb and protects some parts of the stack. If the program overwrites such parts stackcheck.py stops the program and points to the offending line of code.