qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] qemu segfaults at start
@ 2011-09-05  9:04 octane indice
  2011-09-05 12:53 ` Stefan Hajnoczi
  2011-09-05 18:37 ` Mulyadi Santosa
  0 siblings, 2 replies; 9+ messages in thread
From: octane indice @ 2011-09-05  9:04 UTC (permalink / raw)
  To: qemu-devel

Hello

I tried to use qemu on x86-32 in order to emulate x86-32bits.
I did a:
wget http://wiki.qemu.org/download/qemu-0.15.0.tar.gz
tar zxvf qemu-0.15.0.tar.gz
cd qemu-0.15.0
./configure --enable-system --target-list=i386-softmmu
make
sudo make install

then:
qemu disk.img
Segmentation fault

I just have a window that popup then disappear. I tried several options and it 
allways do a segfault.

I tried with the 0.14.1 version, and same results.

What information do you need in order to help me?

Thanks

Envoyé avec Inmano, ma messagerie renversante et gratuite : http://www.inmano.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Qemu-devel] qemu segfaults at start
  2011-09-05  9:04 [Qemu-devel] qemu segfaults at start octane indice
@ 2011-09-05 12:53 ` Stefan Hajnoczi
  2011-09-06  8:11   ` octane indice
  2011-09-05 18:37 ` Mulyadi Santosa
  1 sibling, 1 reply; 9+ messages in thread
From: Stefan Hajnoczi @ 2011-09-05 12:53 UTC (permalink / raw)
  To: octane indice; +Cc: qemu-devel

On Mon, Sep 5, 2011 at 10:04 AM, octane indice <octane@alinto.com> wrote:
> qemu disk.img
> Segmentation fault

Please post the backtrace as well as your host operating system
version (e.g. Fedora 15):

gdb --args qemu disk.img
(gdb) r
...runs and crashes...
(gdb) bt

Stefan

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Qemu-devel] qemu segfaults at start
  2011-09-05  9:04 [Qemu-devel] qemu segfaults at start octane indice
  2011-09-05 12:53 ` Stefan Hajnoczi
@ 2011-09-05 18:37 ` Mulyadi Santosa
  1 sibling, 0 replies; 9+ messages in thread
From: Mulyadi Santosa @ 2011-09-05 18:37 UTC (permalink / raw)
  To: octane indice; +Cc: qemu-devel

On 05/09/2011, octane indice <octane@alinto.com> wrote:
> then:
> qemu disk.img
> Segmentation fault

how about invoking it as:
qemu -hda disk.img
?
does that make any difference? perhaps adding -S too so we could find
out whether it reach the very initial point.....

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Qemu-devel] qemu segfaults at start
  2011-09-05 12:53 ` Stefan Hajnoczi
@ 2011-09-06  8:11   ` octane indice
  2011-09-06  8:39     ` Stefan Weil
  2011-09-06  9:26     ` Stefan Hajnoczi
  0 siblings, 2 replies; 9+ messages in thread
From: octane indice @ 2011-09-06  8:11 UTC (permalink / raw)
  To: Stefan Hajnoczi; +Cc: qemu-devel

En réponse à Stefan Hajnoczi <stefanha@gmail.com> :
> > qemu disk.img
> > Segmentation fault
> 
> Please post the backtrace as well as your host operating
> system
> version (e.g. Fedora 15):
> 
> gdb --args qemu disk.img
> (gdb) r
> ...runs and crashes...
> (gdb) bt
>
Thanks for the help, here the infos:

I run under slackware 13.1
$ gcc -v
Reading specs from /usr/lib/gcc/i486-slackware-linux/4.4.4/specs
Target: i486-slackware-linux
Configured with: ../gcc-4.4.4/configure --prefix=/usr --libdir=/usr/lib --enable-
shared --enable-bootstrap --enable-languages=ada,c,c++,fortran,java,objc --
enable-threads=posix --enable-checking=release --with-system-zlib --with-
python-dir=/lib/python2.6/site-packages --disable-libunwind-exceptions --
enable-__cxa_atexit --enable-libssp --with-gnu-ld --verbose --with-arch=i486 -
-target=i486-slackware-linux --build=i486-slackware-linux --host=i486-
slackware-linux
Thread model: posix
gcc version 4.4.4 (GCC)
$ uname -a
Linux aspireone 2.6.33.4-smp #2 SMP Wed May 12 22:47:36 CDT 2010 i686 
Intel(R) Atom(TM) CPU N270   @ 1.60GHz GenuineIntel GNU/Linux

-I'm remote, so I use vnc, but even in local it does the same.
-In order to prove it's not related to the disk used, I create an empty one for 
the purpose:
$ dd if=/dev/zero of=disk.img bs=1024k count=1


$ gdb --args qemu disk.img -vnc 127.0.0.1:1
GNU gdb (GDB) 7.1
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-slackware-linux".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/bin/qemu...(no debugging symbols 
found)...done.
(gdb) r
Starting program: /usr/local/bin/qemu disk.img -vnc 127.0.0.1:1
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x081a94c1 in ?? ()
(gdb) bt
#0  0x081a94c1 in ?? ()
#1  0xb58af3e7 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) info reg
eax            0xbfffef08       -1073746168
ecx            0x1      1
edx            0x0      0
ebx            0x8      8
esp            0xbfffee50       0xbfffee50
ebp            0xbfffef08       0xbfffef08
esi            0x0      0
edi            0x0      0
eip            0x81a94c1        0x81a94c1
eflags         0x210246 [ PF ZF IF RF ID ]
cs             0x73     115
ss             0x7b     123
ds             0x7b     123
es             0x7b     123
fs             0x0      0
gs             0x33     51
(gdb)

And exact same bt if I launch with qemu -hda disk.img

HTH, thanks


Envoyé avec Inmano, ma messagerie renversante et gratuite : http://www.inmano.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Qemu-devel] qemu segfaults at start
  2011-09-06  8:11   ` octane indice
@ 2011-09-06  8:39     ` Stefan Weil
  2011-09-06 11:18       ` octane indice
  2011-09-06  9:26     ` Stefan Hajnoczi
  1 sibling, 1 reply; 9+ messages in thread
From: Stefan Weil @ 2011-09-06  8:39 UTC (permalink / raw)
  To: octane indice; +Cc: qemu-devel

Am 06.09.2011 10:11, schrieb octane indice:
> $ gdb --args qemu disk.img -vnc 127.0.0.1:1
> GNU gdb (GDB) 7.1
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i486-slackware-linux".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /usr/local/bin/qemu...(no debugging symbols
> found)...done.
> (gdb) r
> Starting program: /usr/local/bin/qemu disk.img -vnc 127.0.0.1:1
> [Thread debugging using libthread_db enabled]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x081a94c1 in ?? ()
> (gdb) bt
> #0  0x081a94c1 in ?? ()
> #1  0xb58af3e7 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> (gdb) info reg
> eax            0xbfffef08       -1073746168
> ecx            0x1      1
> edx            0x0      0
> ebx            0x8      8
> esp            0xbfffee50       0xbfffee50
> ebp            0xbfffef08       0xbfffef08
> esi            0x0      0
> edi            0x0      0
> eip            0x81a94c1        0x81a94c1
> eflags         0x210246 [ PF ZF IF RF ID ]
> cs             0x73     115
> ss             0x7b     123
> ds             0x7b     123
> es             0x7b     123
> fs             0x0      0
> gs             0x33     51
> (gdb)
>
> And exact same bt if I launch with qemu -hda disk.img
>
> HTH, thanks
>    

/usr/local/bin/qemu is stripped because it was installed with make install,
so there is no useful debugging information.

Please look for the unstripped i386-softmmu/qemu executable in your build path
and run it using gdb.

Regards,
Stefan Weil

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Qemu-devel] qemu segfaults at start
  2011-09-06  8:11   ` octane indice
  2011-09-06  8:39     ` Stefan Weil
@ 2011-09-06  9:26     ` Stefan Hajnoczi
  2011-09-06 11:19       ` octane indice
  1 sibling, 1 reply; 9+ messages in thread
From: Stefan Hajnoczi @ 2011-09-06  9:26 UTC (permalink / raw)
  To: octane indice; +Cc: qemu-devel

On Tue, Sep 6, 2011 at 9:11 AM, octane indice <octane@alinto.com> wrote:
> En réponse à Stefan Hajnoczi <stefanha@gmail.com> :
> -In order to prove it's not related to the disk used, I create an empty one for
> the purpose:
> $ dd if=/dev/zero of=disk.img bs=1024k count=1

You can run QEMU completely without a disk, just run:
$ gdb qemu
(gdb) r

I wonder if it crashes that way too.

Stefan

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Qemu-devel] qemu segfaults at start
  2011-09-06  8:39     ` Stefan Weil
@ 2011-09-06 11:18       ` octane indice
  0 siblings, 0 replies; 9+ messages in thread
From: octane indice @ 2011-09-06 11:18 UTC (permalink / raw)
  To: Stefan Weil; +Cc: qemu-devel

En réponse à Stefan Weil <weil@mail.berlios.de> :
> /usr/local/bin/qemu is stripped because it was installed with
> make install,
> so there is no useful debugging information.
> 
> Please look for the unstripped i386-softmmu/qemu executable in
> your build path and run it using gdb.
> 
$ gdb --args /usr/src/qemu-0.15.0/i386-softmmu/qemu disk.img -vnc 
127.0.0.1:1
GNU gdb (GDB) 7.1
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-slackware-linux".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/src/qemu-0.15.0/i386-softmmu/qemu...done.
(gdb) r
Starting program: /usr/src/qemu-0.15.0/i386-softmmu/qemu disk.img -vnc 
127.0.0.1:1
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
raise_interrupt (intno=8, is_int=0, error_code=0, next_eip_addend=0)
    at /usr/src/qemu-0.15.0/target-i386/op_helper.c:1375
1375        env->exception_index = intno;
(gdb) bt
#0  raise_interrupt (intno=8, is_int=0, error_code=0, next_eip_addend=0)
    at /usr/src/qemu-0.15.0/target-i386/op_helper.c:1375
#1  0x081a9b50 in raise_exception_err (exception_index=13, error_code=8)
    at /usr/src/qemu-0.15.0/target-i386/op_helper.c:1386
#2  0xcdb0e012 in ?? ()
#3  0x00000071 in ?? ()
#4  0x0000008f in ?? ()
#5  0x00000000 in ?? ()
(gdb) info reg
eax            0xbfffeee8       -1073746200
ecx            0x1      1
edx            0x0      0
ebx            0x8      8
esp            0xbfffee30       0xbfffee30
ebp            0xbfffeee8       0xbfffeee8
esi            0x0      0
edi            0x0      0
eip            0x81a94c1        0x81a94c1 <raise_interrupt+177>
eflags         0x210246 [ PF ZF IF RF ID ]
cs             0x73     115
ss             0x7b     123
ds             0x7b     123
es             0x7b     123
fs             0x0      0
gs             0x33     51
(gdb)

> Regards,
> Stefan Weil
> 
I hope there's more to understand.
Thanks

Envoyé avec Inmano, ma messagerie renversante et gratuite : http://www.inmano.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Qemu-devel] qemu segfaults at start
  2011-09-06  9:26     ` Stefan Hajnoczi
@ 2011-09-06 11:19       ` octane indice
  2011-09-06 19:29         ` Mulyadi Santosa
  0 siblings, 1 reply; 9+ messages in thread
From: octane indice @ 2011-09-06 11:19 UTC (permalink / raw)
  To: Stefan Hajnoczi; +Cc: qemu-devel

En réponse à Stefan Hajnoczi <stefanha@gmail.com> :
> You can run QEMU completely without a disk, just run:
> $ gdb qemu
> (gdb) r
> 
> I wonder if it crashes that way too.
> 
Yes:
(gdb) r
Starting program: /usr/src/qemu-0.15.0/i386-softmmu/qemu -vnc 127.0.0.1:1
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
raise_interrupt (intno=8, is_int=0, error_code=0, next_eip_addend=0)
    at /usr/src/qemu-0.15.0/target-i386/op_helper.c:1375
1375        env->exception_index = intno;
(gdb)



Envoyé avec Inmano, ma messagerie renversante et gratuite : http://www.inmano.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Qemu-devel] qemu segfaults at start
  2011-09-06 11:19       ` octane indice
@ 2011-09-06 19:29         ` Mulyadi Santosa
  0 siblings, 0 replies; 9+ messages in thread
From: Mulyadi Santosa @ 2011-09-06 19:29 UTC (permalink / raw)
  To: octane indice; +Cc: Stefan Hajnoczi, qemu-devel

On Tue, Sep 6, 2011 at 18:19, octane indice <octane@alinto.com> wrote:
> En réponse à Stefan Hajnoczi <stefanha@gmail.com> :
>> You can run QEMU completely without a disk, just run:
>> $ gdb qemu
>> (gdb) r
>>
>> I wonder if it crashes that way too.
>>
> Yes:
> (gdb) r
> Starting program: /usr/src/qemu-0.15.0/i386-softmmu/qemu -vnc 127.0.0.1:1
> [Thread debugging using libthread_db enabled]
>
> Program received signal SIGSEGV, Segmentation fault.
> raise_interrupt (intno=8, is_int=0, error_code=0, next_eip_addend=0)
>    at /usr/src/qemu-0.15.0/target-i386/op_helper.c:1375
> 1375        env->exception_index = intno;
> (gdb)

"env" is null?

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2011-09-06 19:30 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-05  9:04 [Qemu-devel] qemu segfaults at start octane indice
2011-09-05 12:53 ` Stefan Hajnoczi
2011-09-06  8:11   ` octane indice
2011-09-06  8:39     ` Stefan Weil
2011-09-06 11:18       ` octane indice
2011-09-06  9:26     ` Stefan Hajnoczi
2011-09-06 11:19       ` octane indice
2011-09-06 19:29         ` Mulyadi Santosa
2011-09-05 18:37 ` Mulyadi Santosa

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).