From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re:GDB and 32-bit guests on 64-bit Xen (Phil Winterfield (winterfi)) Date: Thu, 17 Jul 2008 18:10:34 -0700 Message-ID: <487FED8A.9080404@oracle.com> References: <200807180102.m6I126Nn001445@rgminet03.oracle.com> Reply-To: mukesh.rathor@oracle.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200807180102.m6I126Nn001445@rgminet03.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: winterfi@cisco.com List-Id: xen-devel@lists.xenproject.org An alternative is gdbsx. checkout: http://xenbits.xensource.com/ext/debuggers.hg see README-dbg. -mr > Has anyone been successful in connecting gdb to a 32-bit guest while it > is running on a 64 bit hypervisor? I have a 32-bit guest that must run > on a 64-bit hypervisor in order to use the Vt-d and Vmdq features of the > Intel NIC's. The difficulty that I am seeing is that when gdb connects > remotely to the image through the gdb server, it is getting a register > mismatch, apparently because it is looking for 64 bit registers in the > 32 bit image, this despite the fact that I tell gdb that the image is an > 'i386' architecture: > > > > (gdb) set architecture i386 > > The target architecture is assumed to be i386 > > (gdb) target remote 127.0.0.1:9999 > > Remote debugging using 127.0.0.1:9999 > > Couldn't establish connection to remote target > > Remote register badly formatted: > T0506:19e0000002020000;07:0000010000000000;10:0000010000000000;thread:0; > > here: 2020000;07:0000010000000000;10:0000010000000000;thread:0; >