On Tuesday 07 August 2007 06:37, shizheng wrote:
> Hi,all:
>
> I think memory access monitoring is useful in debugging a target
> running in qemu. There are two ways to do this(or even more):
>
> 1.x86 specific. add debug register emulation in qemu.
> 2.hardware independent. such as adding a comman
Hi,all:
I think memory access monitoring is useful in debugging a target
running in qemu. There are two ways to do this(or even more):
1.x86 specific. add debug register emulation in qemu.
2.hardware independent. such as adding a command in qemu monitor.
I would like to know if anybody has alrea
On 8/6/07, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> I don't think adding annotations as snapshots is the right approach. I
> think proper support should be added in the header. I wouldn't be too
> concerned with breaking compatibility in qcow2. That's why it's qcow2
> and not just an updated
[Resending as the last copy seems to have been lost in the ether -- it
certainly isn't in the GMANE archive]
Well, behavior with the patch applied is certainly different.
The large download I'm running still times out; however, it is now able
to resume without needing to bring the interface down
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook 07/08/06 13:19:15
Modified files:
. : gdbstub.c
Log message:
Ensure string is properly terminated.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/gdbstub.c?cvsroot=qemu&r1=1.61
