All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jurij Smakov <jurij@wooyd.org>
To: sparclinux@vger.kernel.org
Subject: Re: mmap breakage
Date: Tue, 07 Dec 2004 06:31:02 +0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0412070128110.12181@bobcat> (raw)
In-Reply-To: <Pine.LNX.4.61.0412032354010.1963@bobcat>

On Mon, 6 Dec 2004, David S. Miller wrote:

> Ok.  On sparc64 32-bit binaries get their ld-linux.so.2 mapped
> at:
>
> davem@nuts:~$ ldd ./nanotest
>        libc.so.6 => /lib/ultra3/libc.so.6 (0x7002c000)
>        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x70000000)
> davem@nuts:~$
>
> On sparc32, TASK_UNMAPPED_BASE is defined per-platform.
> On sun4c it is set to 0xe0000000, on srmmu systems it is
> set to 0x50000000.
>
> So the 0x08000000 address is still a complete mystery to me.

When I run ldd as above, I also get:

kundera:~# ldd ./a.out
         libc.so.6 => /lib/libc.so.6 (0x7002c000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x70000000)

However, that's somehow different from running '/lib/ld-linux.so.2 ./a.out'
(ldd actually does it). Once you invoke ld-linux.so.2 as an executable, 
it's placement is controlled by ELF_ET_DYN_BASE, which is 0x08000000 for 
ELF32 binaries by default.

Best regards,

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC


  parent reply	other threads:[~2004-12-07  6:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04  5:22 mmap breakage Jurij Smakov
2004-12-04 23:13 ` Richard Mortimer
2004-12-04 23:16 ` Richard Mortimer
2004-12-06  4:30 ` Jurij Smakov
2004-12-06  5:23 ` David S. Miller
2004-12-07  6:00 ` Jurij Smakov
2004-12-07  6:06 ` David S. Miller
2004-12-07  6:11 ` Keith M Wesolowski
2004-12-07  6:20 ` David S. Miller
2004-12-07  6:31 ` Jurij Smakov [this message]
2004-12-07  7:47 ` David S. Miller
2004-12-07  8:24 ` Jakub Jelinek
2004-12-07 15:38 ` Jurij Smakov
2004-12-08  0:54 ` Richard Mortimer
2004-12-09  5:24 ` David S. Miller
2004-12-09  7:34 ` David S. Miller

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=Pine.LNX.4.61.0412070128110.12181@bobcat \
    --to=jurij@wooyd.org \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.