NightStar is a suite of debugging and analysis tools for Linux software development. NightStar tools are minimally intrusive, allowing users to locate bugs, find timing bottlenecks, and analyze multi-threaded and multi-process interactions while preserving application execution behavior and determinism. NightStar includes a complete source-level debugger, a trace utility that offers a graphic view of kernel interactions, a data monitor, and a system and application performance tuner.
The jBixbe debugger lets you debug Java applications on the conceptual level of the Unified Modeling Language (UML) at which they are designed and makes it possible to find not only simple bugs but also weaknesses and inefficiencies in application design. It shows the big picture of your application so you can recognize classes and objects, and their relationships and interaction. Different view levels support top-down debugging and simplify debugging of multi-threaded applications. Source code debugging has been fully integrated into the object-oriented visualization.
The XhtmlValidator is a PHP class that can be used to validate XHTML documents. It uses only the expat extension functions, which are always available in PHP, so it does not need other external XML processing extensions. The class parses the documents and checks whether the tags and attributes used by the documents are allowed within the XHTML standard. If validation errors are found, highlighted error messages and offending document line numbers will be returned.
Failmalloc generates a shared library which can be loaded by LD_PRELOAD or linked at compilation time. failmalloc is meant to demonstrate what really happens if memory allocation fails, which is a necessary part of testing the robustness of a program. Failmalloc inserts hooks into your program which induce failures of memory allocation calls. The functions "malloc", "realloc", and "memalign" are hooked, but other functions which use one of these functions are also affected.
slogcxx is a simple C++ logging library for debugging and tracing. It's meant to be easier to use than log4j-based systems. It has an NLOG macro (similar to NDEBUG) that reduces the footprint and disables all logging. The interface is designed to be streamlined with "log << message << somefloat << endl;" calls.