From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Sparc-linux-user problem
Date: Sat, 28 Apr 2007 12:47:26 +0300 [thread overview]
Message-ID: <f43fc5580704280247w6fc9c52tc2f192b8f3fb8652@mail.gmail.com> (raw)
Hi,
I'm investigating why Sparc32 user emulator breaks when linked with
-lrt. It seems that other libraries also cause the problem, for
example -lm -ldl -lX11 -lbfd -lslang is okay, but -lm -ldl -lX11
-lbfd -lslang -lglib-2.0 segfaults just like -lm -lrt. If just address
space conflict was the issue, I'd think 12 megs libbfd would trigger
the problem instead of 64k librt.
Any ideas?
Good output (DEBUG_SIGNAL enabled):
qemu-sparc ./ld-linux.so.2
qemu: SIGSEGV pc=0x810d80b4 address=4103fd10 w=1 oldset=0x80000000
Usage: ld.so [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
You have invoked `ld.so', the helper program for shared library executables.
This program usually lives in the file `/lib/ld.so', and special directives
[cut]
Bad output:
qemu: SIGSEGV pc=0x810d80d4 address=4103fd10 w=1 oldset=0x80000000
qemu: SIGSEGV pc=0x00018000 address=00018000 w=0 oldset=0xfffbfaff
queue_signal: sig=11
qemu: uncaught target signal 11 (Segmentation fault) - exiting
This ld-linux.so.2 is from qemu-tests-0.5.3. The value pc
(=0x810d80d4) changes a bit when libraries are added.
next reply other threads:[~2007-04-28 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 9:47 Blue Swirl [this message]
2007-04-28 17:20 ` [Qemu-devel] Sparc-linux-user problem Paul Brook
2007-04-28 20:39 ` Kevin F. Quinn
2007-04-29 0:24 ` Paul Brook
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=f43fc5580704280247w6fc9c52tc2f192b8f3fb8652@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).