From: Daniel Jacobowitz <drow@false.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb@sourceware.org
Subject: Re: the "load" command and the .bss section
Date: Mon, 28 Apr 2008 13:48:00 -0000 [thread overview]
Message-ID: <20080427135600.GA9356@caradoc.them.org> (raw)
In-Reply-To: <200804270509.34308.vapier@gentoo.org>
On Sun, Apr 27, 2008 at 05:09:31AM -0400, Mike Frysinger wrote:
> i was doing a new board port using jtag and so was leveraging the "load"
> command to setup the initial ELF in the relevant memory regions. things kept
> crashing on me and then i realized that the loading process wasnt actually
> zeroing out the bss. is there a reason for this ? i googled and flipped
> through the manual, but the details on what exactly the "load" command is
> supposed to do is a bit on sketchy side. from what i can tell from the gdb
> source code and the actual output from running the command, it walks the
> section headers (rather than the program headers ?) and loads up everything
> that is in the file. since the bss section doesnt actually exist in the file
> and is only allocated, that is why it gets skipped ?
Load puts things at their LMA rather than their VMA. So it assumes
that whatever sets up load -> virtual also handles bss; it's more like
flash programming than like the Linux kernel's loader. Heck,
sometimes it is flash programming...
IIRC we have a couple of old requests for a version of load which
drops things at their VMA. That one would have to clear the BSS.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-27 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 8:02 Mike Frysinger
2008-04-28 13:48 ` Daniel Jacobowitz [this message]
2008-04-28 17:29 ` Mike Frysinger
2008-04-28 17:42 ` Daniel Jacobowitz
2008-04-29 18:04 ` Michael Snyder
2008-05-01 0:11 ` Mike Frysinger
2008-05-01 2:03 ` Michael Snyder
2008-05-01 3:32 ` Daniel Jacobowitz
2008-05-01 19:24 ` Michael Snyder
2008-05-01 19:32 ` Daniel Jacobowitz
2008-05-01 20:05 ` Michael Snyder
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=20080427135600.GA9356@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=vapier@gentoo.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