From: Mike Frysinger <vapier@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: the "load" command and the .bss section
Date: Mon, 28 Apr 2008 14:07:00 -0000 [thread overview]
Message-ID: <200804272331.21219.vapier@gentoo.org> (raw)
In-Reply-To: <u8wyyzml8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
On Sunday 27 April 2008, Eli Zaretskii wrote:
> > From: Mike Frysinger <vapier@gentoo.org>
> > Date: Sun, 27 Apr 2008 17:45:37 -0400
> > Cc: gdb-patches@sourceware.org
> >
> > ah, now that i know the intentions, may i suggest the following to the
> > documentation.
>
> Thanks, but I'm afraid the text you suggested is not clear enough.
>
> > +The file is loaded according to the load addresses (rather than virtual)
> > as
>
> How is "load address" opposed to "virtual address"? This requires
> explanation.
>
> > +is specified in the executable. It is expected that the target system
> > will +do the actual relocation, and in the process, handle such things as
> > setup of +allocated sections (e.g. the bss).
>
> This is also too cryptic to be useful. Can you (or someone else)
> suggest a more elaborate description? E.g., what is ``relocation'' in
> this context? and what other things besides .bss are expected to be
> set up by loading?
the load description in general implies the reader already has higher
knowledge of these details. i dont see the changes i propose affecting this
in any way. i'm not sure expounding on the lower (and format-specific)
details being appropriate in this context as the final decision is up to the
target bfd, not gdb.
if someone else wants to expand the description, go for it, but i'm fine with
the small additions i've contributed, and i think the issues raised here are
unrelated to the new text.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-04-28 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804270509.34308.vapier@gentoo.org>
[not found] ` <20080427135600.GA9356@caradoc.them.org>
2008-04-28 8:34 ` Mike Frysinger
2008-04-28 8:39 ` Eli Zaretskii
2008-04-28 14:07 ` Mike Frysinger [this message]
2008-04-28 22:54 ` Eli Zaretskii
2008-04-28 19:08 ` Michael Snyder
2008-04-29 1:10 ` Eli Zaretskii
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=200804272331.21219.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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