From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: sur5r@sur5r.net
Subject: [Qemu-devel] qemu-x86_64 on i386 host: SIGSEGV
Date: Sun, 24 Mar 2013 14:43:51 +0400 [thread overview]
Message-ID: <514ED8E7.7090600@msgid.tls.msk.ru> (raw)
$ ./x86_64-linux-user/qemu-x86_64 bash64
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation Fault
$ gdb x86_64-linux-user/qemu-x86_64
(gdb) ru bash64
Program received signal SIGSEGV, Segmentation fault.
disas_insn (s=s@entry=0xffffcf98, pc_start=18446744073699066880)
at target-i386/translate.c:4107
4107 b = ldub_code(s->pc);
(gdb) p *s
$1 = {override = -1, prefix = 1484501952, aflag = 1, dflag = 1484503884,
pc = 18446744073699066880, is_jmp = 0, cs_base = 0, pe = 1, code32 = 1,
lma = 1, code64 = 1, rex_x = 0, rex_b = 0, ss32 = 1, cc_op = 0, addseg = 0,
f_st = 0, vm86 = 0, cpl = 3, iopl = 0, tf = 0, singlestep_enabled = 0,
jmp_opt = 1, mem_index = 0, flags = 4243635, tb = 0xf50e9f88,
popl_esp_hack = 0, rip_offset = 0, cpuid_features = 126614521,
cpuid_ext_features = -2139086847, cpuid_ext2_features = 563194873,
cpuid_ext3_features = 101}
This is with current git. Previous versions (tried 1.1 and 1.4)
segfaults in the same place too.
Some binaries works - for example, gzip (it prints "qemu: Unsupported syscall:
202" on the way which is a different issue).
Thanks,
/mjt
next reply other threads:[~2013-03-24 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 10:43 Michael Tokarev [this message]
2013-03-24 10:59 ` [Qemu-devel] qemu-x86_64 on i386 host: SIGSEGV Peter Maydell
2013-03-24 13:24 ` Michael Tokarev
2013-03-25 15:03 ` Richard Henderson
2013-03-25 15:36 ` Laurent Desnogues
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=514ED8E7.7090600@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=sur5r@sur5r.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.