public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: SOFUN_ADDRESS_MAYBE_MISSING
Date: Tue, 07 Oct 2003 04:24:00 -0000	[thread overview]
Message-ID: <vt23ce5vfpz.fsf@zenia.home> (raw)
In-Reply-To: <200310061242.h96CgtiA000454@elgar.kettenis.dyndns.org>


Mark Kettenis <kettenis@chello.nl> writes:
> I'm wondering what to do with SOFUN_ADDRESS_MAYBE_MISSING.  It started
> out (and still largely is) a hack to work around a problem with
> stabs-in-ELF with Sun's C compiler.  Later it also got enabled on some
> Linux variants, to work around a bug in HJ's Linux binutils IIRC.

Not that this is germane to the issue you're trying to fix, but:

SOFUN_ADDRESS_MAYBE_MISSING isn't a bug --- it's a feature.  Sun made
various adjustments to make fewer stabs require relocation, to reduce
link time.  That's why line number stabs are relative to the beginning
of the function, for example.  Since every function has a linker
symbol for its entry point, and there are STT_FILE symbols for the
compilation units (I think I've got that right), there's no real need
to put the address in the SO and FUN stabs, too.

  parent reply	other threads:[~2003-10-07  4:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 12:42 SOFUN_ADDRESS_MAYBE_MISSING Mark Kettenis
2003-10-06 16:44 ` SOFUN_ADDRESS_MAYBE_MISSING Kevin Buettner
2003-10-07 16:44   ` SOFUN_ADDRESS_MAYBE_MISSING Jim Blandy
2003-10-07  4:24 ` Jim Blandy [this message]
2003-10-15 18:21 ` SOFUN_ADDRESS_MAYBE_MISSING Elena Zannoni
2003-10-16 19:49   ` SOFUN_ADDRESS_MAYBE_MISSING Mark Kettenis
2003-10-15 18:44 SOFUN_ADDRESS_MAYBE_MISSING Michael Elizabeth Chastain

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=vt23ce5vfpz.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).