That's what I was looking for.
thanks,
david
Uri Lublin wrote:
> Avi Kivity wrote:
>> david ahern wrote:
>>
>>> Attaching gdb to qemu you work with addresses as seen by the qemu
>>> process; the
>>> idea is to work with addresses as seen inside the guest.
>>>
>>>
>>> Now, if you attach gdb to
Avi Kivity wrote:
> david ahern wrote:
>
>> Attaching gdb to qemu you work with addresses as seen by the qemu process;
>> the
>> idea is to work with addresses as seen inside the guest.
>>
>>
>> Now, if you attach gdb to the qemu process,
>>
>> gdb /usr/local/bin/qemu-system-x86_64 2346
>>
>
david ahern wrote:
> Attaching gdb to qemu you work with addresses as seen by the qemu process; the
> idea is to work with addresses as seen inside the guest.
>
> For example, in the qemu console you can examine guest kernel memory such as
> task structs using guest kernel based addresses:
>
> (qem
Attaching gdb to qemu you work with addresses as seen by the qemu process; the
idea is to work with addresses as seen inside the guest.
For example, in the qemu console you can examine guest kernel memory such as
task structs using guest kernel based addresses:
(qemu) x /128w 0xc0327a80
c
david ahern wrote:
> Does anyone know of tools that can dump memory for a qemu guest with addresses
> as seen by the guest and generate a core file? For instance, say you know the
> guest is running a 32-bit linux kernel with a 1G/3G split. Then you would want
> to dump 1G of memory starting 0xc000
Does anyone know of tools that can dump memory for a qemu guest with addresses
as seen by the guest and generate a core file? For instance, say you know the
guest is running a 32-bit linux kernel with a 1G/3G split. Then you would want
to dump 1G of memory starting 0xc000 and create an ELF core
