public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: david ahern <daahern@cisco.com>
To: Uri Lublin <uril@qumranet.com>, Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: tools to dump guest memory and generate core file
Date: Tue, 18 Mar 2008 18:19:37 -0600	[thread overview]
Message-ID: <47E05C19.8030608@cisco.com> (raw)
In-Reply-To: <47DF8BB5.7090407@qumranet.com>

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 the qemu process,
>>>
>>> gdb /usr/local/bin/qemu-system-x86_64 2346
>>>       
>> I meant connecting to the gdb stub in qemu that represents the guest:
>>
>>   (gdb) target remote localhost:1234
>>
>> Of course, it means starting qemu with the gdb stub enabled.  We might
>> add a monitor command to start it after the fact.
>>   
> gdbserver is the monitor command you're looking for:
> (qemu) help gdbserver
> gdbserver [port] -- start gdbserver session (default port=1234)
> 
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-03-19  0:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17  3:02 tools to dump guest memory and generate core file david ahern
2008-03-17  8:59 ` Avi Kivity
2008-03-17 23:36   ` david ahern
2008-03-18  6:15     ` Avi Kivity
2008-03-18  9:30       ` Uri Lublin
2008-03-19  0:19         ` david ahern [this message]

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=47E05C19.8030608@cisco.com \
    --to=daahern@cisco.com \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=uril@qumranet.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox