This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Getting .debug_frame Dwarf info without outputtings all the other debug info sections?
- From: Matt Hoosier <matt dot hoosier at gmail dot com>
- To: gcc-help at gcc dot gnu dot org
- Date: Tue, 3 Jul 2012 16:49:14 +0000 (UTC)
- Subject: Re: Getting .debug_frame Dwarf info without outputtings all the other debug info sections?
- References: <CAJgxT3_HuJg=7QpE8i24X5fz2x4PV0ZbiokAbojDMDXLaiFRnw@mail.gmail.com> <mcry5q9ognp.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
Ian Lance Taylor <iant <at> google.com> writes:
>
> If really all you want is a backtrace, the debugger should be able to do
> that using the unwind tables.
>
> I believe that the google branch in GCC's svn repository has a -gmlt
> option that may do what you want.
>
> Ian
>
>
Hmm, the CodeSourcery prebuilt ARM stack I'm using doesn't directly include it,
but I wonder: does Gold just generally handle VM pressure from large amounts of
debug info (or whatever other ELF sections) better? Maybe that would be worth a
try?