> On 1 Dec 2016, at 21:13, Peter Maydell <peter.mayd...@linaro.org> wrote:
> You need a QCOW2 disk to store the snapshots on, ...
> Taking savevm snapshots doesn't need any cooperation
> from the guest OS ..
> I don't know whether anybody's tested this with M profile:
does your Stellaris board support this?
assuming I fix my devices to save their status and I can correctly resume from
a given snapshot, I still fail to understand how to integrate this feature in
the usual debugging workflow.
the way GNU ARM Eclipse QEMU is currently used is similar to any JTAG connected
physical board, the user starts a GDB client that connects to QEMU as a GDB
server, writes the 'flash' content and then steps through the code. there is
really no difference from a physical board. with a properly configured Eclipse,
the user has nothing special to do, only select either SEGGER J-Link or QEMU,
the rest is automatic.
the second use case is to run unit tests, when a script starts QEMU in
semihosting mode, passes the elf file, and get an exit code and an XML with the
detailed test results. once the script is functional it can be repeatedly
executed by continuous integration servers, and there can be no interaction
with QEMU during the tests.
what would be a debug scenario that uses snapshots?