From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: qemu-devel@nongnu.org
Cc: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: reverse-{debugging,continue} not working on v7.2.0, i386 guest
Date: Wed, 18 Jan 2023 06:14:33 +0000 [thread overview]
Message-ID: <Y8eOSedPWlOjriho@localhost> (raw)
Hello QEMU folks.
I was struggling to fix a recent heisenbug in the Linux kernel,
and fortunately the bug was reproducible with TCG and -smp 1.
I'm using qemu version 7.2.0, and guest architecture is i386.
I tried to inspect the bug using record/replay and reverse-debugging
feature in the QEMU.
recorded with:
qemu-system-i386 \
-icount shift=auto,rr=record,rrfile=$REPLAY_FILE \
-kernel arch/x86/boot/bzImage \
-cpu SandyBridge \
-initrd debian-i386.cgz \
-smp 1 \
-m 1024 \
-nographic \
-net none \
-append "page_owner=on console=ttyS0"
and replayed with:
qemu-system-i386 \
-icount shift=auto,rr=replay,rrfile=$REPLAY_FILE \
-kernel arch/x86/boot/bzImage \
-cpu SandyBridge \
-initrd debian-i386.cgz \
-smp 1 \
-m 1024 \
-nographic \
-net none \
-s \
-append "page_owner=on console=ttyS0"
(I'm using a initrd image instead of a disk file.)
The record and replay works well. The bug is reliably reproduced
when relaying. but when I try to reverse-continue or reverse-stepi after
kernel panic, the gdb only says:
"remote failure reply 'E14'"
Is there something I'm missing, or record/replay do not work with
QEMU v7.2.0 or i386?
--
Best regards,
Hyeonggon
next reply other threads:[~2023-01-18 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 6:14 Hyeonggon Yoo [this message]
2023-01-18 7:12 ` reverse-{debugging,continue} not working on v7.2.0, i386 guest Pavel Dovgalyuk
2023-01-18 8:47 ` Hyeonggon Yoo
2023-01-18 9:39 ` Pavel Dovgalyuk
2023-01-19 4:40 ` Hyeonggon Yoo
2023-01-19 9:28 ` Pavel Dovgalyuk
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=Y8eOSedPWlOjriho@localhost \
--to=42.hyeyoo@gmail.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--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 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.