Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: John Haller <jhaller@lucent.com>
Cc: Daniel Berlin <dan@cgsoftware.com>,
	jtc@redback.com, Christopher Faylor <cgf@redhat.com>,
	gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: stabs vs. dwarf-2 for C programs
Date: Fri, 13 Apr 2001 08:09:00 -0000	[thread overview]
Message-ID: <m2eluwn8fj.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <3AD70931.CF488A07@lucent.com>

John Haller <jhaller@lucent.com> writes:

> Daniel Berlin wrote:
> 
> > The pre-linker pass is on my list of things to do, after all the
> > optimized code debugging support and finishing the work on the new
> > register allocator for gcc.
> 
> The native Sun Solaris linker takes an interesting approach
> to eliminating duplicate debugging information.  It does
> not copy much debug information from the original object
> module to the final linked product, just enough to identify
> which original object contains the debugging information.
> The debugger then needs to locate the original object module
> when setting breakpoints or looking up symbol information.
> The only downside is that this prevents much symbolic debugging
> if the original built objects aren't around.  It can also
> speed the link not only by not having to rewrite symbolic
> debug information, but also by not having to read it in the
> original objects.  It also speeds up starting the debugger,
> as the debugger no longer has to read the entire symbol table
> at startup.

We already don't do this anyway, without needing to do this kind of
hairy trick.

DWARF2 was made to be able to be quickly scanned, and not entirely
loaded all at once.

> 
> I'm glad to see other people looking at this, because in
> my spare time it could take years to work on this myself.
> -- 
> John Haller jhaller@lucent.com

-- 
One night a jet flew a little bit too close to my house.  I was
walking from the living room to the kitchen, and the stewardess
told me to sit down.


  reply	other threads:[~2001-04-13  8:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 19:13 J.T. Conklin
2001-04-12 19:17 ` Christopher Faylor
2001-04-12 19:31   ` J.T. Conklin
2001-04-12 19:59     ` Daniel Berlin
2001-04-13  7:13       ` John Haller
2001-04-13  8:09         ` Daniel Berlin [this message]
2001-04-13 16:18           ` Ian Lance Taylor
2001-04-13 18:39             ` Daniel Berlin
2001-04-13 20:22               ` Ian Lance Taylor
2001-04-13 22:01                 ` Daniel Berlin
2001-04-13 22:19                   ` Ian Lance Taylor
2001-04-13 22:37                     ` DJ Delorie
2001-04-13 23:31                     ` Daniel Berlin
2001-04-13 23:47                       ` Daniel Berlin
2001-04-13 23:51                       ` Ian Lance Taylor
2001-04-13 22:56                   ` Daniel Berlin
2001-04-13 23:40                     ` Ian Lance Taylor
2001-04-13 23:55                   ` Todd Whitesel
2001-04-12 19:55 ` Daniel Berlin
2001-04-12 23:37   ` Eli Zaretskii
2001-04-13  8:13     ` Daniel Berlin
2001-04-12 22:00 ` Geoff Keating
2001-04-12 22:37   ` Daniel Berlin

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=m2eluwn8fj.fsf@dynamic-addr-83-177.resnet.rochester.edu \
    --to=dan@cgsoftware.com \
    --cc=binutils@sources.redhat.com \
    --cc=cgf@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jhaller@lucent.com \
    --cc=jtc@redback.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