Re: gdb cross compilation, error from gdb/tui module

paawan oza
2010-10-28T11:13:21Z

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 <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: paawan oza <paawan1982@yahoo.com>; Baurzhan Ismagulov <ibr@radix50.net>
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