From: Hui Zhu <teawater@gmail.com>
To: Terry Guo <flameroc@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Reverse debugging for arm baremetal targets?
Date: Mon, 22 Jul 2013 07:26:00 -0000 [thread overview]
Message-ID: <CANFwon3Uaqv+Tah6wU2MupoZ+LNnb=pv2MzNVSBmEm+2FfW84Q@mail.gmail.com> (raw)
In-Reply-To: <CAGbRaL4_DQ9fYXX8pj6x8rwXbMBsS7ZCi2D2jj_hSSvv-iZfdA@mail.gmail.com>
On Mon, Jul 22, 2013 at 2:10 PM, Terry Guo <flameroc@gmail.com> wrote:
> On Mon, Jul 22, 2013 at 10:07 AM, Hui Zhu <teawater@gmail.com> wrote:
>> On Mon, Jul 22, 2013 at 9:37 AM, Terry Guo <flameroc@gmail.com> wrote:
>>> Hi there,
>>>
>>> Is this feature enabled for arm baremetal targets? If not, is it
>>> possible to do so and what kind of problems we need to solve to
>>> achieve this? Thanks in advance for your help.
>>>
>>> Best Regards,
>>> Terry
>>
>> If just for reverse debug, I think it is not depend on the arch. So I
>> think it is OK for ARM.
>>
>> And if I remember is right, simics support it.
>>
>> Thanks,
>> Hui
>
> Thanks for your reply. I did some tests and it seems to me that
> reverse debugging doesn't work for baremetal targets. My test includes
> a ARM Cortex-M3 board running a baremetal program, a gdb server and a
> baremetal gdb. The gdb version is:
>
> GNU gdb (GDB) 7.6
>
> After I connect to M3 board and run command "record", I got:
This error is about process record but not reverse debug.
>
> Breakpoint 1, main () at main.cpp:24
> 24 xyz = 0;
> (gdb) record
> Process record: the current architecture doesn't support record function.
This is the reason why you cannot use reverse debug commands.
You got this error is because:
/* Reversible debugging, process record. */
set_gdbarch_process_record (gdbarch, arm_process_record);
This line is called in arm_linux_init_abi but you are not a linux target.
I found all the "set_gdbarch_process_record" is called in
xxx_linux_init function make it depend on Linux.
I forget why I do it. :P
I think 2 reasons let me do it:
1. syscall record just support linux.
2. make it can pass review. :P
But most of prec function is just to record the behavior of
instruction. So maybe we can move it to arch init code.
Thanks,
Hui
> (gdb) show ar
> architecture args arm
> (gdb) show architecture
> The target architecture is set automatically (currently arm)
> (gdb) n
> 26 foo ();
> (gdb) s
> foo () at main.cpp:16
> 16 xyz = 1;
> (gdb) n
> 17 return bar ();
> (gdb) s
> bar () at main.cpp:10
> 10 xyz = 2;
> (gdb) reverse-next
> Target remote does not support this command.
>
> Am I doing something wrong? Please advise.
>
> BR,
> Terry
prev parent reply other threads:[~2013-07-22 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 1:37 Terry Guo
2013-07-22 2:08 ` Hui Zhu
2013-07-22 6:10 ` Terry Guo
2013-07-22 6:38 ` Jan Kratochvil
2013-07-22 7:30 ` Yao Qi
2013-07-22 7:34 ` Hui Zhu
2013-07-22 7:26 ` Hui Zhu [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='CANFwon3Uaqv+Tah6wU2MupoZ+LNnb=pv2MzNVSBmEm+2FfW84Q@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=flameroc@gmail.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