From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: jimb@red-bean.com, gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] Deal with -g1 generated DWARF2 debug info
Date: Wed, 07 Dec 2005 16:19:00 -0000 [thread overview]
Message-ID: <200512062255.jB6Mt2IL001600@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20051204230646.GA26122@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 4 Dec 2005 18:06:46 -0500)
> Date: Sun, 4 Dec 2005 18:06:46 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> > > Mark, FYI, we ended up removing all dwarf sections other than
> > > .debug_frame. This plus .symtab are enough to make backtraces useful;
> > > it works quite well and avoids the undertested -g1.
> >
> > Hmm, perhaps we're just lucky, but it seems that all supported OpenBSD
> > platforms have no problem with -g1. I'll keep your idea in mind as
> > plan B. Doesn't it result in gdb printing the wrong function names
> > for static function names in backtraces?
>
> No. It gets those from .symtab; that's why we left it in.
Bleah, turns out we were using ld -x on the object files before
building them into a library. Of course this made local symbols
disappear from .symtab.
Anyway, it seems that my fellow OpenBSD developers are happy with
compiling all system libraries with -g, which of course is much better
;-).
I'll send a message to the GCC mailing list about -g1 & DWARF2.
Mark
next prev parent reply other threads:[~2005-12-06 22:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 22:05 Mark Kettenis
2005-12-04 22:31 ` Jim Blandy
2005-12-05 9:43 ` Mark Kettenis
2005-12-04 22:40 ` Jim Blandy
2005-12-04 23:06 ` Daniel Jacobowitz
2005-12-04 23:07 ` Jim Blandy
2005-12-05 10:32 ` Daniel Jacobowitz
2005-12-05 18:29 ` Mark Kettenis
2005-12-05 19:23 ` Daniel Jacobowitz
2005-12-07 16:19 ` Mark Kettenis [this message]
2005-12-05 16:56 ` Mark Kettenis
2005-12-05 19:57 ` Daniel Jacobowitz
2005-12-05 14:40 ` Mark Kettenis
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=200512062255.jB6Mt2IL001600@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.com \
/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