From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6503 invoked by alias); 21 Aug 2006 18:32:56 -0000 Received: (qmail 6490 invoked by uid 22791); 21 Aug 2006 18:32:54 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 21 Aug 2006 18:32:49 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GFEZp-0006nv-HW; Mon, 21 Aug 2006 14:32:45 -0400 Date: Mon, 21 Aug 2006 18:32:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: Cai Qian , gdb@sourceware.org Subject: Re: Virtual Machine and GDB Message-ID: <20060821183245.GA26071@nevyn.them.org> Mail-Followup-To: Michael Snyder , Cai Qian , gdb@sourceware.org References: <20060821000736.GA2596@nevyn.them.org> <44E9E787.9010202@cse.unl.edu> <1156184892.8438.18.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1156184892.8438.18.camel@localhost.localdomain> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00170.txt.bz2 On Mon, Aug 21, 2006 at 11:28:12AM -0700, Michael Snyder wrote: > OK, so you have two issues: > 1) You need to get gdbserver running in your VM, and provide > some means for gdbserver to talk to a gdb that is running in the > outside world. Unles you have access to a serial port, the > obvious way to do this is to get a IP stack running in the VM, > assign it an IP address, and let gdbserver open up a socket. > Then gdb (running somewhere outside of the VM) can attach to > the socket. What sort of VM are we talking about here? I think a lot of the responses have been assuming different meanings for that term. If it's a bytecode language, like a Java Virtual Machine, then you don't want this at all. You would have to have multiple processes in the VM, plus an internal debug interface allowing one process to debug another. Instead, think of it more like a simulator; the virtual machine monitor can talk directly to GDB. If it's a whole system simulator, more like qemu or vmware, then maybe you want to have a stub running on the inside. -- Daniel Jacobowitz CodeSourcery