From: Andi Kleen <ak@linux.intel.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu user x86 working?
Date: Fri, 11 Feb 2011 14:27:30 -0800 [thread overview]
Message-ID: <4D55B7D2.6010206@linux.intel.com> (raw)
In-Reply-To: <AANLkTikKDNRGiBU+7RonvaQ09qv9_p=GFdGvP30be3Zf@mail.gmail.com>
> I don't have any problems running a statically linked x86_64
> helloworld program in an i386 chroot. Dynamically linked programs try
> to use wrong libraries, but at least running
> /lib64/ld-linux-x86-64.so.2 directly works.
static binary segfaults too. I wonder if it's some setup on my system.
I tried disabling the usual suspects like address randomization, but
that didn't change things.
Or could it be the compiler (gcc 4.5)?
I remember using this quite some time ago (years).
-Andi
next prev parent reply other threads:[~2011-02-11 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 19:49 [Qemu-devel] qemu user x86 working? Andi Kleen
2011-02-11 22:05 ` Blue Swirl
2011-02-11 22:27 ` Andi Kleen [this message]
2011-02-12 1:04 ` Mulyadi Santosa
2011-02-12 8:08 ` Blue Swirl
2011-02-15 12:20 ` Andi Kleen
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=4D55B7D2.6010206@linux.intel.com \
--to=ak@linux.intel.com \
--cc=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).