python-tracing provides the Python library "tracing" to help with logging debug messages. This module provides a couple of functions for logging debug messages. It is sometimes practical to add a lot of debugging log messages to a program, but having them enabled all the time results in very large log files. Also, logging that much takes quite a bit of time. This module provides a way to turn such debugging or tracing messages on and off, based on the filename in which they occur.
SystemTap is a tracing and probing tool that allows users to study and monitor the activities of the computer system in fine detail. It provides information similar to the output of tools like netstat, ps, top, and iostat; however, SystemTap is designed to provide more filtering and analysis options for collected information. It can be used as a performance monitoring tool, and is most useful when other tools cannot precisely pinpoint a bottleneck in the system, requiring a deep analysis of kernel activity. Application developers can also use it to monitor, in finer detail, how their application behaves within the Linux system.
libcsdbg is a C++ exception stack tracer. When an exception is thrown, caught, and handled, libcsdbg offers the tools to create and process the exception stack trace, the path the exception has propagated up the call stack, unwinding it up to the section were it was handled. The traces are detailed with demangled function signatures and additional addr2line information (the source code file and line from which each function was called). libcsdbg can use all the well-known objective code file formats (a.out, elf, coff, ecoff, etc.) and can easily be used as the base for your own instrumentation code. libcsdbg transparently loads the symbol tables of the chosen dynamic libraries and of the executable, demangles function symbols to complete signatures, and binds function names to runtime addresses (even for the DSO symbols).
jTracer is a visualization tool for libcsdbg. When libcsdbg creates a stack trace for a caught exception, a thread, or a process-wide stack trace dump, it can be configured to broadcast the trace data through TCP/IP (UDP/IP, RS-232, USB, etc. are under development). jTracer catches those data and visualizes them to the user, sorted and ordered by TCP/UDP/IP address/port (or serial port), process ID, and executable, thread, and timestamp. It's particularly useful when you're doing cross-development and your target platform has no resources to visualize output. The rationale behind the development of jTracer is similar to gdb/gdbserver functionality.