Summary: | Add support for MiniDebugInfo (.gnu_debugdata) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sam James <sam> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | arsen, eschwartz, esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=920745 https://bugs.kde.org/show_bug.cgi?id=492429 https://github.com/oracle/dtrace-utils/issues/96 https://sourceware.org/bugzilla/show_bug.cgi?id=31884 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 933986 |
Description
Sam James
![]() ![]() ![]() ![]() The idea here would be that we implement it under some FEATURES flag at first, then do it by default unconditionally (or at least on-by-default). It doesn't have much value if users have to opt-in to it. The overhead is also very low. It's intended to _not_ be a replacement for full debug information. dev-debug/valgrind doesn't support it, although I don't think that's a blocker for this (filed https://bugs.kde.org/show_bug.cgi?id=492429). dev-debug/dtrace is likely to add support (https://github.com/oracle/dtrace-utils/issues/96). One decision to make is if we include symtab *and* line number information. The line number information makes it a fair bit bigger although still nothing like DWARF. |