From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27977 invoked by alias); 28 Oct 2010 11:13:21 -0000 Received: (qmail 27965 invoked by uid 22791); 28 Oct 2010 11:13:20 -0000 X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,TW_QE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from nm9-vm0.bullet.mail.sp2.yahoo.com (HELO nm9-vm0.bullet.mail.sp2.yahoo.com) (98.139.91.196) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Thu, 28 Oct 2010 11:13:15 +0000 Received: from [98.139.91.62] by nm9.bullet.mail.sp2.yahoo.com with NNFMP; 28 Oct 2010 11:13:13 -0000 Received: from [98.139.91.7] by tm2.bullet.mail.sp2.yahoo.com with NNFMP; 28 Oct 2010 11:13:13 -0000 Received: from [127.0.0.1] by omp1007.mail.sp2.yahoo.com with NNFMP; 28 Oct 2010 11:13:13 -0000 Received: (qmail 81227 invoked by uid 60001); 28 Oct 2010 11:13:13 -0000 Message-ID: <428402.79807.qm@web112503.mail.gq1.yahoo.com> Received: from [123.237.140.102] by web112503.mail.gq1.yahoo.com via HTTP; Thu, 28 Oct 2010 04:13:12 PDT References: <877394.75835.qm@web112505.mail.gq1.yahoo.com> <185221.64370.qm@web112515.mail.gq1.yahoo.com> <954946.73290.qm@web112515.mail.gq1.yahoo.com> <201010281118.10136.pedro@codesourcery.com> Date: Thu, 28 Oct 2010 11:13:00 -0000 From: paawan oza Subject: Re: gdb cross compilation, error from gdb/tui module To: Pedro Alves Cc: Baurzhan Ismagulov , gdb@sourceware.org In-Reply-To: <201010281118.10136.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-10/txt/msg00118.txt.bz2 If you want to work on the linux part as well, and if running a native arm gdb is too much for your arm board, you can use process record on x86 connected to an arm-linux gdbserver ("target remote ...") running on the arm board. That'll be slow, but should work. Oza: 1) as I do not have arm target/board, everything to be done on host either by vmware, qemu et... whichever support arm-linux-kernel on x86 host...and then inside that I can compile gdb fully for arm and do linux ABI part, hope that way it works out. but I ahev not got any setup as of now, as I am working on the first part on arm insns. (non-OS-ABI part) 2) If I correctly understand, the nomenclature 'arm-tdep', does it mean arm-target-depedent, and when I try to compile gdb with --target=arm-eabi or arm-elf, it also compile arm-tdep.c as a packge of simulator. Is My understanding correct ? Thank you for your inputs. Regards, Oza. ----- Original Message ---- From: Pedro Alves To: gdb@sourceware.org Cc: paawan oza ; Baurzhan Ismagulov Sent: Thu, October 28, 2010 3:48:09 PM Subject: Re: gdb cross compilation, error from gdb/tui module On Thursday 28 October 2010 10:43:11, paawan oza wrote: > If I try > ./configure --host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi > --build=i686-pc-linux-gnu --disable-tui > and build gdb that means.... > > -> gdb is able to rn on loinux host with x86 arch ? Yes. > -> and using target sim command I can debug arm binaries. ? No, --target=arm-none-linux-gnueabi does not include "target sim". Look at gdb/configure.tgt for "gdb_sim=../sim/arm". You'll need --target=arm-eabi or arm-elf. > -> but if modify arm-tdep.c then will I be able to test the implementation > (process record, non-linux-ABI part) ? Supposedly. If you want to work on the linux part as well, and if running a native arm gdb is too much for your arm board, you can use process record on x86 connected to an arm-linux gdbserver ("target remote ...") running on the arm board. That'll be slow, but should work. -- Pedro Alves