9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8l vs. acid?
Date: Wed, 22 Jun 2005 17:54:36 -0400	[thread overview]
Message-ID: <db5e51a8e4df2f54b7af1178e1db1646@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.BSI.4.61.0506221015560.5014@malasada.lava.net>

There are fixes on sources for this.
It's caused by there not really being any difference in the
a.out layout between the bootable kernel image and a plain
executable.

I'd not noticed that before, but to tell the truth I can't
remember ever wanting to look at the data part of a boot image
file (as opposed to the data part of a loaded boot image).

Thanks.

--jim

On Wed Jun 22 16:25:54 EDT 2005, newsham@lava.net wrote:
> Hi,
>     I'm seeing some strange behavior in the linking and debugging
> of a small program of mine:
>     http://lava.net/~newsham/quest/
> 
> When I build it and inspect it in acid, it shows the map as:
>    {{"text", 0x80100020, 0x80100041, 0x00000020},
>     {"data", 0x80100041, 0x80100049, 0x00000041}}
> 
> and indeed I see the data starting at 0x80100041.  However
> the relocation values in the binary and the symbol table
> both think that the "hello" variable starts at 0x80101000.
> 
> Now if I change the -T0x80100020 to -T0x100020 the map is
> even stranger:
>    {{"text", 0x00001020, 0x00001041, 0x00000020},
>     {"data", 0x00002000, 0x00002008, 0x00000041}}
> 
> however, the symbols say that the _main and hello are at
> 0x100020 and 0x101000 respectively.
> 
> What gives?  Who's to blame here, libmach?
> 
> Tim Newsham
> http://www.lava.net/~newsham/


      parent reply	other threads:[~2005-06-22 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 20:24 Tim Newsham
2005-06-22 20:44 ` Tim Newsham
2005-06-22 21:54 ` jmk [this message]

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=db5e51a8e4df2f54b7af1178e1db1646@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).