> -Original Message-
> From: Greg Clayton
> Sent: Thursday, April 9, 2020 6:32 PM
> To: Robinson, Paul
> Cc: dwarf-discuss@lists.dwarfstd.org
> Subject: Re: [Dwarf-Discuss] Selectively strip CUs from .debug_info?
>
> Not aware of any tools that can do this, but can't you just do this
Not aware of any tools that can do this, but can't you just do this in your
build?:
- link once with full .o files and save debug info off
- strip debug info from all third party .o files and link again. You still get
all debug info for any .o files you didn't strip
> On Apr 9, 2020, at
Not aware of that specific tool - though debugger load time can be greatly
improved by the use of some kind of debugger index. If their debugger of
choice is GDB, then -ggnu-pubnames + -Wl,-gdb-index (with gold or lld) has
made things pretty usable for my needs in LLVM development, and seems to
Does anyone know of a tool that can strip debug info for specified
CUs from an executable? I'm not aware of a way to do this, but
there are many things I'm not aware of.
The use case is someone who wants to build the entire program
(which includes a number of 3rd-party libraries) with debug
"quality of implementation" thing - but in general, even if a few bugs were
fixed/improvements were made to both Clang and GCC, it's going to be
hard/impossible to track certain things through templates in DWARF - for
similar reasons that it's hard to provide diagnostic messages that describe
I wasn't on the list when I originally sent this message, and it didn't show
up in the archive, so I'm sending it again. Sorry if there's duplication:
Hi!
I'm currently working on a debugger which consumes dwarf information
and I noticed a possible discrepancy between output from popular
