From: Ralf Baechle <ralf@oss.sgi.com>
To: K.H.C.vanHouten@kpn.com
Cc: Adrian Bunk <bunk@fs.tum.de>,
linux-mips@oss.sgi.com, K.H.C.vanHouten@research.kpn.com
Subject: Re: Compile error with current CVS kernel
Date: Tue, 13 Mar 2001 15:22:36 +0100 [thread overview]
Message-ID: <20010313152236.B1208@bacchus.dhis.org> (raw)
In-Reply-To: <200103130746.IAA07580@sparta.research.kpn.com>; from K.H.C.vanHouten@research.kpn.com on Tue, Mar 13, 2001 at 08:46:43AM +0100
On Tue, Mar 13, 2001 at 08:46:43AM +0100, Houten K.H.C. van (Karel) wrote:
> Hope this helps.
Against my low blood pressure - yes ...
> LOAD off 0x0000000000000000 vaddr 0x0000000000001000 paddr
> 0x0000000000001000 align 2**12
> filesz 0x000000000000a184 memsz 0x000000000000a184 flags r--
This PT_LOAD entry shouldn't even exist ...
> LOAD off 0x000000000000b000 vaddr 0xffffffff88002000 paddr
> 0xffffffff88002000 align 2**12
> filesz 0x00000000001acd10 memsz 0x00000000001d25a4 flags rwx
> 15 .kstrtab 00007c24 0000000000001b00 0000000000001b00 00000b00 2**2
> CONTENTS, ALLOC, LOAD, READONLY, DATA
> 16 __ksymtab 00001a60 0000000000009724 0000000000009724 00008724 2**2
> CONTENTS, ALLOC, LOAD, READONLY, DATA
That's scary - these sections are explicitly mentioned in the linker
script and yet ld places them near address zero. Oh pleassure, oh
garbage.
This can probably be fixed by changing the ldscript; can experiment what
it takes to get your ld to place all sections with a LOAD attribute placed
next to each other? My ld behaves fine.
Ralf
next prev parent reply other threads:[~2001-03-13 16:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 21:56 Compile error with current CVS kernel Adrian Bunk
2001-03-12 21:56 ` Adrian Bunk
2001-03-12 23:15 ` Ralf Baechle
2001-03-12 23:15 ` Ralf Baechle
2001-03-13 7:46 ` Houten K.H.C. van (Karel)
2001-03-13 13:53 ` Ralf Baechle
2001-03-13 14:22 ` Ralf Baechle [this message]
2001-03-13 18:18 ` Karel van Houten
2001-03-13 18:18 ` Karel van Houten
2001-03-13 18:27 ` Ralf Baechle
2001-03-13 18:27 ` Ralf Baechle
2001-03-13 18:38 ` Karel van Houten
2001-03-13 18:38 ` Karel van Houten
2001-03-13 18:40 ` Karel van Houten
2001-03-13 18:40 ` Karel van Houten
2001-03-13 21:15 ` Pete Popov
2001-03-21 17:39 ` Adrian Bunk
2001-03-21 17:39 ` Adrian Bunk
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=20010313152236.B1208@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=K.H.C.vanHouten@kpn.com \
--cc=K.H.C.vanHouten@research.kpn.com \
--cc=bunk@fs.tum.de \
--cc=linux-mips@oss.sgi.com \
/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.