From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-37545-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 17374 invoked by alias); 18 Jun 2010 18:47:54 -0000
Received: (qmail 17364 invoked by uid 22791); 18 Jun 2010 18:47:54 -0000
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 18 Jun 2010 18:47:48 +0000
Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167])	by smtp-outbound-1.vmware.com (Postfix) with ESMTP id DC3001307C;	Fri, 18 Jun 2010 11:47:46 -0700 (PDT)
Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138])	by mailhost2.vmware.com (Postfix) with ESMTP id D440E8E78C;	Fri, 18 Jun 2010 11:47:46 -0700 (PDT)
Message-ID: <4C1BBF52.1010603@vmware.com>
Date: Fri, 18 Jun 2010 18:47:00 -0000
From: Michael Snyder <msnyder@vmware.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090609)
MIME-Version: 1.0
To: Jerry 85032 <jerry85032@gmail.com>
CC: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Newbie gdb / gdbserver question with x86-64 and -m32 g++ goodness
References: <28922383.post@talk.nabble.com> <4C1BA085.2010607@vmware.com> <28929351.post@talk.nabble.com>
In-Reply-To: <28929351.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2010-06/txt/msg00074.txt.bz2


> ==============================
> 
> Assuming it is i386:x86-64, setting archi to i386, then connecting
> note: on the gdb side, the executable has been loaded with file
> 
> $ gdb 
> GNU gdb Fedora (6.8-37.el5)
> This GDB was configured as "x86_64-redhat-linux-gnu".
> (gdb) set archi i386:x86-64
> The target architecture is assumed to be i386:x86-64
> (gdb) file hello
> Reading symbols from /home/j/hello...done.
> (gdb) show archi
> The target architecture is assumed to be i386:x86-64
> (gdb) target extended-remote rdev6:2010
> Remote debugging using rdev6:2010
> [New Thread 32667]
> Cannot access memory at address 0x800000008
> (gdb) 

This is the closest to success.  So use this "set archi" setting.

At this point you are running into a second failure:

	Cannot access memory at address 0x800000008

I don't know what that one is about.