Your message dated Fri, 16 Dec 2022 10:10:25 +0300
with message-id <[email protected]>
and subject line Re: qemu-x86_64 segfaults when run some x64 binaries on i386
system
has caused the Debian Bug report #703825,
regarding qemu-x86_64 segfaults when run some x64 binaries on i386 system
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
703825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703825
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-user, qemu-user-static
Version: 1.1.2+dfsg-1
Severity: normal
Tags: upstream, confirmed
Forwarded: http://thread.gmane.org/gmane.comp.emulators.qemu/202103
$ ./x86_64-linux-user/qemu-x86_64 bash64
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
$ 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.
--- End Message ---
--- Begin Message ---
Version: 1:5.2+dfsg-1
This has been fixed long time ago, it seems. At least the version in bullseye
works fine. Closing this bug report.
/mjt
--- End Message ---
