From: Jim Blandy <jimb@redhat.com>
To: Klee Dienes <klee@apple.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add stabs entries for coalesced symbols.
Date: Sun, 24 Nov 2002 14:22:00 -0000 [thread overview]
Message-ID: <vt27kf21v7l.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <F99ABA98-FF96-11D6-B9B6-00039396EEB8@apple.com>
I like these docs a lot better, thanks.
Klee Dienes <klee@apple.com> writes:
> (speaking of
> which, I should mention that these docs are extensively plagiarized
> from docs written by another engineer at Apple; I'm just adapting them
> as best I can from the release notes for use in the stabs document)
Does that engineer have an assignment on file? Or does Apple have a
blanket assignment in place?
> +The static link editor divides up a coalesced section on the
> +boundaries of the symbols in that section, associating the bytes of
> +the section after each symbol with the preceding symbol. An object
> +file is considered malformed if a coalesced section does not have a
> +symbol at the first address of the section.
> +
> +To allow the linker to properly manage the debug information for
> +coalesced symbols, the stabs entries for a given coalesced symbol must
> +be preceded by @code{N_BNSYM} and terminated with @code{N_ENSYM}.
> +These stabs must be at the start and end of the given coalesced
> +symbol, respectively.
That is:
the value of the N_BNYSM stab should be the start address of the
coalesced portion (the same value as the symbol that begins the
portion), and the value of the N_ENSYM stab should be the end address
of the coalesced prtion (the same value as the next coalesced symbol,
or the end of the whole coalesced section).
If that's right, then please include that language, or something
equally explicit; I'm happy to see this committed.
next prev parent reply other threads:[~2002-11-24 22:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C774777A-FB47-11D6-84AF-00039396EEB8@apple.com>
2002-11-18 16:37 ` Klee Dienes
2002-11-18 22:22 ` Ian Lance Taylor
2002-11-24 2:25 ` Klee Dienes
2002-11-24 6:21 ` Eli Zaretskii
2002-12-08 17:00 ` Klee Dienes
2002-12-08 22:39 ` Eli Zaretskii
2002-12-09 10:22 ` Klee Dienes
2002-12-09 12:37 ` Eli Zaretskii
2002-11-24 9:46 ` Ian Lance Taylor
2002-11-24 14:22 ` Jim Blandy [this message]
2002-12-06 8:59 ` Nick Clifton
2002-11-18 22:59 Eli Zaretskii
[not found] <1038196445.11584.ezmlm@sources.redhat.com>
2002-11-24 20:21 ` Jim Ingham
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=vt27kf21v7l.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=klee@apple.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