From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10279 invoked by alias); 23 Jan 2003 19:12:50 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10269 invoked from network); 23 Jan 2003 19:12:48 -0000 Received: from unknown (HELO gate1.itt.com) (151.190.254.100) by 172.16.49.205 with SMTP; 23 Jan 2003 19:12:48 -0000 Received: from no.name.available by gate1.itt.com via smtpd (for [66.187.233.205]) with SMTP; 23 Jan 2003 19:12:48 UT Received: by fwdcmail2.fwdc.de.ittind.com with Internet Mail Service (5.5.2653.19) id ; Thu, 23 Jan 2003 14:12:47 -0500 Message-ID: From: "Gopen, Josh" To: gdb@sources.redhat.com Subject: compiling gdb to examine core files from a target(non-native) arc hitecture. Date: Thu, 23 Jan 2003 19:12:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2003-01/txt/msg00404.txt.bz2 Hello everyone, I am interested in compiling a version of gdb on a i686-redhat-linux platform to read a core file dumped on a arm-linux platform. I have tried making a cross debugger specifying --build=i686-redhat-linux, --host=i686-redhat-linux, and --target=arm-linux for the configure script. I have been unable to fool gdb into thinking that its host is a arm-linux while producing a i686-redhat-linux binary. Has anyone tried this? Is this possible (with or without messy hacks)? I only want to read a static core file I do not want to run an executable. Thanks, Josh Gopen Software Engineer ITT Aerospace/Communications josh.gopen@itt.com ************************************ If this email is not intended for you, or you are not responsible for the delivery of this message to the addressee, please note that this message may contain ITT Privileged/Proprietary Information. In such a case, you may not copy or deliver this message to anyone. You should destroy this message and kindly notify the sender by reply email. Information contained in this message that does not relate to the business of ITT is neither endorsed by nor attributable to ITT. ************************************