From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] New category: dev-debug
Date: Sun, 07 Jan 2024 13:48:43 +0100 [thread overview]
Message-ID: <25e92c7126ffcc566c1cb1fb671de16d706ff4fa.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
Hi,
I'd like to propose adding a new dev-debug category. The description
could be:
Code debuggers and debugging-related tools.
Potential candidates include:
dev-util/ald: Assembly Language Debugger
dev-util/apitrace: Tool for tracing, analyzing, and debugging graphics APIs
dev-util/bpftrace: High-level tracing language for eBPF
dev-util/cgdb: A curses front-end for GDB, the GNU debugger
dev-util/d-feet: D-Feet is a powerful D-Bus debugger
dev-util/d-spy: D-spy is a blisteringly fast D-Bus debugger
dev-util/ddd: Graphical front-end for command-line debuggers
dev-util/edb-debugger: edb is a cross platform x86/x86-64 debugger, inspired by Ollydbg
dev-util/kdbg: Graphical debugger interface
dev-util/leaktracer: Trace and analyze memory leaks in C++ programs
dev-util/lldb: The LLVM debugger
dev-util/ltrace: trace library calls made at runtime
dev-util/pretrace: start dynamically linked applications under debugging environment
dev-util/pwndbg: A GDB plug-in that makes debugging with GDB suck less
dev-util/strace: Useful diagnostic, instructional, and debugging tool
dev-util/sysdig: A system exploration and troubleshooting tool
dev-util/systemtap: A linux trace/probe tool
dev-util/valgrind: An open-source memory debugger for GNU/Linux
media-gfx/renderdoc: A stand-alone graphics debugging tool
sys-devel/gdb: GNU debugger
sys-devel/gdb-apple: Apple branch of the GNU Debugger, Developer Tools 4.3
This was originally prompted by bug 920438 [1], pointing out that LLDB
and GDB belong to the same category. dev-util/ currently carries 428
packages, so I suppose it makes sense to split it some more, especially
when we can clearly distinguish some more specific groups.
[1] https://bugs.gentoo.org/920438
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next reply other threads:[~2024-01-07 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 12:48 Michał Górny [this message]
2024-01-07 13:20 ` [gentoo-dev] [RFC] New category: dev-debug Sam James
2024-01-07 13:30 ` Michał Górny
2024-01-10 8:23 ` Florian Schmaus
2024-01-10 11:01 ` Sam James
2024-01-10 11:09 ` Florian Schmaus
2024-01-10 13:41 ` Viorel Munteanu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25e92c7126ffcc566c1cb1fb671de16d706ff4fa.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox