From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IXdWS-0006UF-Nl
	for qemu-devel@nongnu.org; Tue, 18 Sep 2007 09:53:52 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IXdWR-0006Tb-4B
	for qemu-devel@nongnu.org; Tue, 18 Sep 2007 09:53:52 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IXdWQ-0006TY-VB
	for qemu-devel@nongnu.org; Tue, 18 Sep 2007 09:53:50 -0400
Received: from fk-out-0910.google.com ([209.85.128.191])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <ronald645@gmail.com>) id 1IXdWQ-0002Iv-Fi
	for qemu-devel@nongnu.org; Tue, 18 Sep 2007 09:53:50 -0400
Received: by fk-out-0910.google.com with SMTP id 19so3347659fkr
	for <qemu-devel@nongnu.org>; Tue, 18 Sep 2007 06:53:49 -0700 (PDT)
Message-ID: <46EFD842.7070207@gmail.com>
Date: Tue, 18 Sep 2007 15:53:06 +0200
From: Ronald <ronald645@gmail.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Insta-segfault! i386-linux-user
References: <1190118724.9564.49.camel@phantasm.home.enterpriseandprosperity.com>
In-Reply-To: <1190118724.9564.49.camel@phantasm.home.enterpriseandprosperity.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: thayne@c2.net, qemu-devel@nongnu.org

Thayne Harbaugh schreef:
> Has anyone seen an insta-segfault with i386-linux-user qemu?  I've
> compiled qemu-0.9.0 as well as qemu-cvs (2007-09-18) with gcc-3.4 and
> -fno-strict-aliasing on an amd64 and I get this:
>
> ./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 ()
>
> Nice NULL frame there - and it's before main() is reached.
>
> Install prefix    /usr
> BIOS directory    /usr/share/qemu
> binary directory  /usr/bin
> Manual directory  /usr/share/man
> ELF interp prefix /usr/gnemul/qemu-%M
> Source path       /home/thayne/dev/c2/qemu-0.9.0
> C compiler        gcc-3.4
> Host C compiler   gcc (also tried with gcc-3.4)
> make              make
> install           install
> host CPU          x86_64
> host big endian   no
> target list       i386-linux-user arm-linux-user
> gprof enabled     no
> profiler          no
> static build      no
> SDL support       yes
> SDL static link   yes
> mingw32 support   no
> Adlib support     yes
> CoreAudio support no
> ALSA support      yes
> DSound support    no
> FMOD support      no
> kqemu support     yes
> Documentation     yes
>
> CFLAGS            -Wall -fno-strict-aliasing -Wall -ggdb -fno-strict-aliasing
> libc              2.6.1-1 (debian lenny)
>
>
>
>
>
>   
Yes, I had this problem too. U only compiled the program using the 
'user' parameters. But to get the virtualisation going, you need to 
compile at least one 'softmmu' (whatever that is). Doing that will 
create the executable: qemu    (this is the executable you want :)   )

So I run Linux and I compile it with (and I really need it):

i386-linux-user AND i386-softmmu     (i386 can be replaced with your 
arch such as: ppc, sparc, x86_64, mips, mipsel and arm)

That should create an executable called qemu (as stated before) which 
should not segfault immediatly lol :)

                                              Good Luck :)