This is the mail archive of the
mailing list for the GDB project.
Re: the "load" command and the .bss section
- From: Michael Snyder <msnyder at specifix dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Mike Frysinger <vapier at gentoo dot org>, drow at false dot org, gdb-patches at sourceware dot org
- Date: Mon, 28 Apr 2008 11:34:13 -0700
- Subject: Re: the "load" command and the .bss section
- References: <email@example.com> <20080427135600.GA9356@caradoc.them.org> <firstname.lastname@example.org> <email@example.com>
On Mon, 2008-04-28 at 06:26 +0300, Eli Zaretskii wrote:
> > From: Mike Frysinger <firstname.lastname@example.org>
> > Date: Sun, 27 Apr 2008 17:45:37 -0400
> > Cc: email@example.com
> > 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
> > +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?
I extend a cautionary rejoinder -- "load" means different things
in different contexts.
I have not looked at this recently, but the last time I did,
there were several different implementations of the "load"
command, and they did not all behave identically, particularly
with regard to the concept of VMA vs. LMA.
That's one reason it hasn't been well documented -- it is
not particularly well defined.