> user space with a fork/freeze approach. > something like fork-events if the checkpoint mechanism is designed for > I couldn't tell what feature needs to be negotiated but I suspect it's
> checkpoint: can't find fork function in inferior. > The other option I found was checkpoints which seem to predate support > so I guess that would need an extension to the stub protocol to support? > You can't do that when your target is `remote' > debugging support but attempting to use them from the gdbstub reports: > As far as I can tell bookmarks where added as part of GDB's reverse > there are two interfaces gdb supports: bookmarks and checkpoints. > see what the best way to integrate this would be.
> QEMU can quite easily snapshot the entire VM state so I was looking to > execution history until you get to the right point. > although currently each step backwards requires replaying the entire Once you get the right command line it works well enough > I have working with Pavel's latest patches for supporting virtio with > I've been playing around with QEMU's reverse debugging support which To: Alex Bennée, gdb, QEMU Developers, Luis Machado 16:49 ` Luis Machado 1 sibling, 0 replies 7+ messages in threadįrom: Pavel Dovgalyuk 6:12 UTC ( / raw) 16:06 Best approach for supporting snapshots for QEMU's gdbstub? Alex 6:12 ` Pavel Dovgalyuk * Re: Best approach for supporting snapshots for QEMU's gdbstub? However I do worry that might lead to snapshots Snapshots each time we hit an event, for example each time we hit a The other thing would be to be more intelligent on QEMU's side and save Qemu.sstep= command which could be used manually. We could of course just add a custom monitor command like the Something like fork-events if the checkpoint mechanism is designed for I couldn't tell what feature needs to be negotiated but I suspect it's The other option I found was checkpoints which seem to predate supportĬheckpoint: can't find fork function in inferior. So I guess that would need an extension to the stub protocol to support? You can't do that when your target is `remote' There are two interfaces gdb supports: bookmarks and checkpoints.Īs far as I can tell bookmarks where added as part of GDB's reverseĭebugging support but attempting to use them from the gdbstub reports: See what the best way to integrate this would be. QEMU can quite easily snapshot the entire VM state so I was looking to Once you get the right command line it works well enoughĪlthough currently each step backwards requires replaying the entireĮxecution history until you get to the right point. I have working with Pavel's latest patches for supporting virtio with I've been playing around with QEMU's reverse debugging support which To: gdb, QEMU Developers, Pavel Dovgalyuk, Luis Machado 16:49 ` Luis Machado 0 siblings, 2 replies 7+ messages in thread
Best approach for supporting snapshots for QEMU's gdbstub? archive mirror help / color / mirror / Atom feed * Best approach for supporting snapshots for QEMU's gdbstub? 16:06 Alex Bennée