From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Miao Qingjun <qmiao@centecnetworks.com>,
user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] UML 2.6.17 problems (section mismatch, get_skas_faultinfo : failed to wait for SIGUSR1/SIGTRAP)
Date: Sun, 9 Jul 2006 15:47:04 +0200 [thread overview]
Message-ID: <200607091547.04527.blaisorblade@yahoo.it> (raw)
In-Reply-To: <006401c69c19$eb9edbd0$d4190a0a@centecnetworks.com>
On Friday 30 June 2006 09:50, Miao Qingjun wrote:
> Hi,
>
> Two problems
>
> First one,
> when building kernel and LKMs,
> WARNING: vmlinux - Section mismatch: reference to .init.text: from .plt
> after '' (at offset 0x8347e44) WARNING: vmlinux - Section mismatch:
> reference to .init: from .plt after '' (at offset 0x8347e64) WARNING:
> vmlinux - Section mismatch: reference to .init.setup: from .plt after ''
> (at offset 0x8347ea4) WARNING: vmlinux - Section mismatch: reference to
> .init.text:nosmp from .plt after '' (at offset 0x8347f20) WARNING: vmlinux
> - Section mismatch: reference to .init.setup:__setup_nosmp from .plt after
> '' (at offset 0x8347f28) WARNING: vmlinux - Section mismatch: reference to
> .init.text:maxcpus from .plt after '' (at offset 0x8347f2c) ...
> ...
>
> So when gdb loads LKM symbols, it seems .init.text and .exit.text sections
> overlapped with .text section.
It isn't a problem we haven't fully analized but which always seemed
harmless - but building with dynamic linking disabled makes it go away.
However, note that it is a kernel build helper (not binutils) which doesn't
know that .plt sections, which are needed for dynamic linking are allowed to
reference .init* sections (while it knows this for other sections). Its
purpose is simply to avoid .text referencing .init, since such a reference
will fail when .init code and data get freed (soon after the boot).
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2006-07-09 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 7:50 [uml-devel] UML 2.6.17 problems (section mismatch, get_skas_faultinfo : failed to wait for SIGUSR1/SIGTRAP) Miao Qingjun
2006-06-30 13:45 ` [uml-devel] [uml-user] " Jeff Dike
2006-07-01 0:38 ` Miao Qingjun
2006-07-07 0:45 ` Jeff Dike
2006-07-07 2:22 ` Daniel Gryniewicz
2006-07-07 3:15 ` Jeff Dike
2006-07-09 13:56 ` Blaisorblade
2006-07-09 13:47 ` Blaisorblade [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=200607091547.04527.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=qmiao@centecnetworks.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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