From mboxrd@z Thu Jan 1 00:00:00 1970 From: Uri Lublin Subject: Re: tools to dump guest memory and generate core file Date: Tue, 18 Mar 2008 11:30:29 +0200 Message-ID: <47DF8BB5.7090407@qumranet.com> References: <47DDDF43.9020008@cisco.com> <47DE32EF.5090903@qumranet.com> <47DF0066.1090602@cisco.com> <47DF5E00.7040700@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Avi Kivity To: david ahern Return-path: In-Reply-To: <47DF5E00.7040700@qumranet.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org 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/