From: paawan oza <paawan1982@yahoo.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Baurzhan Ismagulov <ibr@radix50.net>, gdb@sourceware.org
Subject: Re: gdb cross compilation, error from gdb/tui module
Date: Thu, 28 Oct 2010 11:13:00 -0000 [thread overview]
Message-ID: <428402.79807.qm@web112503.mail.gq1.yahoo.com> (raw)
In-Reply-To: <201010281118.10136.pedro@codesourcery.com>
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
next prev parent reply other threads:[~2010-10-28 11:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 15:36 gdb cross compilation, error from gdb/tui module.... please help paawan oza
2010-10-27 16:14 ` Baurzhan Ismagulov
2010-10-28 4:02 ` gdb cross compilation, error from gdb/tui module.... please help. <readline comilation error after disabling tui> paawan oza
2010-10-28 9:43 ` gdb cross compilation, error from gdb/tui module paawan oza
2010-10-28 10:18 ` Pedro Alves
2010-10-28 11:13 ` paawan oza [this message]
2010-10-28 11:27 ` Pedro Alves
2010-10-28 11:57 ` paawan oza
2010-10-28 12:11 ` Pedro Alves
2010-10-28 12:46 ` paawan oza
2010-10-28 13:11 ` Pedro Alves
2010-10-28 14:06 ` paawan oza
2010-10-28 15:14 paawan oza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=428402.79807.qm@web112503.mail.gq1.yahoo.com \
--to=paawan1982@yahoo.com \
--cc=gdb@sourceware.org \
--cc=ibr@radix50.net \
--cc=pedro@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox