From: Yao Qi <yao@codesourcery.com>
To: gdb@sourceware.org
Subject: Re: how to test arm-tdep.c (with cross compiled gdbserver) using gdbserver ?
Date: Mon, 25 Jul 2011 04:48:00 -0000 [thread overview]
Message-ID: <4E2CF585.6090902@codesourcery.com> (raw)
In-Reply-To: <1311566182.99397.YahooMailRC@web112507.mail.gq1.yahoo.com>
On 07/25/2011 11:56 AM, paawan oza wrote:
> I have done following, and with that should be able to test arm-reversible
> stuffs with gdbserver.
>
>> > ./configure --target=arm-linux <which will compile gdb for x86 takes arm
>> >dependent code into build>
>> > make
>> > cd gdb
>> > cd gdbserver
>> > ./configure --host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi
> <above will preparegbserver for target, whihc could be later copied to arm
> board>
>
That looks right to me. You have to build a gdb for arm, as you did
above, and then cross-compile gdbserver for arm-linux.
> there are other targets such as arm-eabi, arm-elf.
> but I am using arm-linux, hope thats ok and it works.
IMO, it works, since your reverse code on arm shares among these arm-*
targets. Testing your code on arm-linux should cover other arm-* targets.
However, there may be some corner cases, such as svc instruction, that
may behave a little different on bare-mental targets (arm-eabi, arm-elf)
and linux targets (arm-linux). I am not familiar with reverse
debugging, so I don't know how much affect of this difference to reverse
debugging. (I might be wrong, of course.)
--
Yao (é½å°§)
prev parent reply other threads:[~2011-07-25 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 7:08 paawan oza
2011-07-25 3:56 ` paawan oza
2011-07-25 4:48 ` Yao Qi [this message]
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=4E2CF585.6090902@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
/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