{"category":{"categoryid":1560,"name":"dev-debug"},"packages":[{"categoryid":1560,"description":"Tool for tracing, analyzing, and debugging graphics APIs","firstseen":"2024-01-19T14:58:22.505355","name":"apitrace","packageid":76957},{"categoryid":1560,"description":"High-level tracing language for eBPF","firstseen":"2024-01-19T14:58:22.505355","name":"bpftrace","packageid":76958},{"categoryid":1560,"description":"A curses front-end for GDB, the GNU debugger","firstseen":"2024-01-13T10:07:51.771505","name":"cgdb","packageid":76900},{"categoryid":1560,"description":"D-Feet is a powerful D-Bus debugger","firstseen":"2024-01-19T14:58:22.505355","name":"d-feet","packageid":76959},{"categoryid":1560,"description":"D-Spy is a simple tool to explore D-Bus connections","firstseen":"2024-01-19T14:58:22.505355","name":"d-spy","packageid":76960},{"categoryid":1560,"description":"Graphical front-end for command-line debuggers","firstseen":"2024-01-18T14:51:54.470540","name":"ddd","packageid":76951,"summary":"GNU DDD is a graphical front-end for command-line debuggers such as GDB, DBX, WDB, Ladebug, JDB, XDB, the Perl debugger, the bash debugger, or the Python debugger. Besides ``usual'' front-end features such as viewing source texts, DDD has become famous through its interactive graphical data display, where data structures are displayed as graphs."},{"categoryid":1560,"description":"Programmable debugger","firstseen":"2024-08-27T22:26:52.330575","name":"drgn","packageid":77709},{"categoryid":1560,"description":"Dynamic BPF-based system-wide tracing tool","firstseen":"2024-08-18T23:08:35.953295","name":"dtrace","packageid":77690},{"categoryid":1560,"description":"DUMA (Detect Unintended Memory Access) is a memory debugging library","firstseen":"2024-01-19T14:58:22.505355","name":"duma","packageid":76961,"summary":"DUMA is an open-source library (under GNU General Public License) to detect buffer overruns and under-runs in C and C++ programs. This library is a fork of Buce Perens Electric Fence library and adds some new features to it."},{"categoryid":1560,"description":"edb is a cross platform x86\/x86-64 debugger, inspired by Ollydbg","firstseen":"2024-01-18T14:51:54.470540","name":"edb-debugger","packageid":76952},{"categoryid":1560,"description":"GNU debugger","firstseen":"2024-01-13T10:07:51.771505","name":"gdb","packageid":76897},{"categoryid":1560,"description":"GDB Enhanced Features for exploit devs & reversers","firstseen":"2024-01-18T14:51:54.470540","name":"gef","packageid":76955,"summary":"GEF is a set of commands for x86\/64, ARM, MIPS, PowerPC and SPARC to assist exploit developers and reverse-engineers when using old school GDB. It provides additional features to GDB using the Python API to assist during the process of dynamic analysis and exploit development. Application developers will also benefit from it, as GEF lifts a great part of regular GDB obscurity, avoiding repeating traditional commands, or bringing out the relevant information from the debugging runtime."},{"categoryid":1560,"description":"Full-fledged graphical interface to operate gprofng","firstseen":"2024-08-31T06:29:52.152361","name":"gprofng-gui","packageid":77716},{"categoryid":1560,"description":"Graphical debugger interface","firstseen":"2024-01-18T14:51:54.470540","name":"kdbg","packageid":76953},{"categoryid":1560,"description":"Trace and analyze memory leaks in C++ programs","firstseen":"2024-01-19T14:58:22.505355","name":"leaktracer","packageid":76962},{"categoryid":1560,"description":"trace library calls made at runtime","firstseen":"2024-01-19T14:58:22.505355","name":"ltrace","packageid":76963},{"categoryid":1560,"description":"Python Exploit Development Assistance for GDB","firstseen":"2024-01-18T14:51:54.470540","name":"peda","packageid":76956},{"categoryid":1560,"description":"A GDB plug-in that makes debugging with GDB suck less","firstseen":"2024-01-18T14:51:54.470540","name":"pwndbg","packageid":76954,"summary":"pwndbg is a GDB plug-in that makes debugging with GDB suck less, with a focus on features needed by low-level software developers, hardware hackers, reverse-engineers and exploit developers."},{"categoryid":1560,"description":"Kernel module for dev-debug\/sysdig","firstseen":"2024-01-19T14:58:22.505355","name":"scap-driver","packageid":76967},{"categoryid":1560,"description":"Useful diagnostic, instructional, and debugging tool","firstseen":"2024-01-19T14:58:22.505355","name":"strace","packageid":76964},{"categoryid":1560,"description":"A system exploration and troubleshooting tool","firstseen":"2024-01-19T14:58:22.505355","name":"sysdig","packageid":76965},{"categoryid":1560,"description":"Linux trace\/probe tool","firstseen":"2024-01-19T14:58:22.505355","name":"systemtap","packageid":76966},{"categoryid":1560,"description":"An open-source memory debugger for GNU\/Linux","firstseen":"2024-01-13T18:09:53.829789","name":"valgrind","packageid":76909,"summary":"Valgrind is a GPL'd tool to help you find memory-management problems in your programs. When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc\/new\/free\/delete are intercepted. As a result, Valgrind can detect problems such as - Use of uninitialised memory - Reading\/writing memory after it has been free'd - Reading\/writing off the end of malloc'd blocks - Reading\/writing inappropriate areas on the stack - Memory leaks -- where pointers to malloc'd blocks are lost forever - Passing of uninitialised and\/or unaddressible memory to system calls - Mismatched use of malloc\/new\/new [] vs free\/delete\/delete [] - Some abuses of the POSIX Pthreads API"}]}