From: Thayne Harbaugh <thayne@c2.net>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Insta-segfault! i386-linux-user
Date: Tue, 18 Sep 2007 15:49:23 -0600 [thread overview]
Message-ID: <1190152163.9564.81.camel@phantasm.home.enterpriseandprosperity.com> (raw)
In-Reply-To: <CBFECEFB-D5C5-4F8C-9AAB-F96DCD9DF326@suse.de>
On Tue, 2007-09-18 at 21:11 +0200, Alexander Graf wrote:
> On Sep 18, 2007, at 8:25 PM, Thayne Harbaugh wrote:
>
> > On Tue, 2007-09-18 at 15:53 +0200, Ronald wrote:
> >> Thayne Harbaugh schreef:
<SNIP>
> >>> ./i386-linux-user/qemu-i386 --help
> >>> Segmentation fault
> >>>
> >>>> From GDB:
> >>>
> >>> Program received signal SIGSEGV, Segmentation fault.
> >>> 0x0000000000000000 in ?? ()
> >>> (gdb) bt
> >>> #0 0x0000000000000000 in ?? ()
> >>> #1 0x00000000600575ed in __libc_csu_init ()
> >>> #2 0x00002b826c660ade in __libc_start_main () from /lib/libc.so.6
> >>> #3 0x00000000600050e9 in _start ()
<SNIP>
>
> We had this on the list some months ago.
I'll dig for that.
> As far as I recall this
> correctly the problem is the linker script. Just take a look at the
> suse source rpm where we replace that one, so it works with x86_64.
Thanks for the guidance.
> Be prepared for breakage though, as linux-user on 64-Bit hosts does
> not work properly.
What about it doesn't work properly? Do you have some links for the
list archives?
Thank you.
next prev parent reply other threads:[~2007-09-18 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 12:32 [Qemu-devel] Insta-segfault! i386-linux-user Thayne Harbaugh
2007-09-18 13:53 ` Ronald
2007-09-18 18:25 ` Thayne Harbaugh
2007-09-18 19:11 ` Alexander Graf
2007-09-18 21:49 ` Thayne Harbaugh [this message]
2007-09-18 22:07 ` Alexander Graf
2007-09-18 22:41 ` J. Mayer
2007-09-18 22:57 ` Alexander Graf
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=1190152163.9564.81.camel@phantasm.home.enterpriseandprosperity.com \
--to=thayne@c2.net \
--cc=agraf@suse.de \
--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).