From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] current cvs debug message (win32 host)
Date: Wed, 04 Aug 2004 04:11:19 +0200 [thread overview]
Message-ID: <pan.2004.08.04.02.11.19.757643@reply.to> (raw)
running qemu.exe in gdb :
Program received signal SIGSEGV, Segmentation fault.
0x362e3020 in ?? ()
(gdb) info reg
eax 0x36 54
ecx 0xa 10
edx 0x0 0
ebx 0x554d4551 1431127377
esp 0x15ffbd0 0x15ffbd0
ebp 0x15ffe14 0x15ffe14
esi 0x4 4
edi 0x15ffc7c 23067772
eip 0x362e3020 0x362e3020
eflags 0x10202 66050
cs 0x17f 383
ss 0x187 391
ds 0x187 391
es 0x187 391
fs 0x3f97 16279
gs 0x0 0
fctrl 0xffff037f -64641
fstat 0xffff0000 -65536
ftag 0xffffffff -1
fiseg 0x17f 383
fioff 0xb00b882b -1341421525
foseg 0xffff0187 -65145
fooff 0x15ff4a8 23065768
---Type <return> to continue, or q <return> to quit---
fop 0x15c 348
(gdb) bt
#0 0x362e3020 in ?? ()
#1 0x00401179 in ?? ()
#2 0x004011aa in ?? ()
#3 0xbff8b537 in ?? ()
#4 0xbff8b3e9 in ?? ()
#5 0xbff89dac in ?? ()
#6 0xffffffff in ?? ()
Cannot access memory at address 0xffffffff
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x362e3020 in ?? ()
(gdb) c
Continuing.
Program exited with code 037777777777.
Windows (98) cryptic error report :
QEMU a causé une défaillance de page dans
le module <inconnu> à 0000:362e3020.
Registres :
EAX=00000036 CS=017f EIP=362e3020 EFLGS=00010202
EBX=554d4551 SS=0187 ESP=0160fbd0 EBP=0160fe14
ECX=0000000a DS=0187 ESI=00000004 FS=3f5f
EDX=00000000 ES=0187 EDI=0160fc7c GS=0000
Octets à CS : EIP :
État de la pile :
6d20302e 74696e6f 2d20726f 70797420 68272065 27706c65 726f6620 726f6d20
6e692065 6d726f66 6f697461 01000a6e 00000004 0160fc7c 0162475c 00404c25
reply other threads:[~2004-08-04 2:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pan.2004.08.04.02.11.19.757643@reply.to \
--to=look@reply.to \
--cc=daimon55@free.fr \
--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).