From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=42093 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Po1Sk-00036u-HU for qemu-devel@nongnu.org; Fri, 11 Feb 2011 17:27:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Po1Si-0003WT-TH for qemu-devel@nongnu.org; Fri, 11 Feb 2011 17:27:37 -0500 Received: from mga09.intel.com ([134.134.136.24]:30470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Po1Si-0003WC-NG for qemu-devel@nongnu.org; Fri, 11 Feb 2011 17:27:36 -0500 Message-ID: <4D55B7D2.6010206@linux.intel.com> Date: Fri, 11 Feb 2011 14:27:30 -0800 From: Andi Kleen MIME-Version: 1.0 Subject: Re: [Qemu-devel] qemu user x86 working? References: <20110211194953.GA19467@tassilo.jf.intel.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel@nongnu.org > 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