From: Hui Zhu <teawater@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Terry Guo <flameroc@gmail.com>,
gdb@sourceware.org
Subject: Re: Reverse debugging for arm baremetal targets?
Date: Mon, 22 Jul 2013 07:34:00 -0000 [thread overview]
Message-ID: <CANFwon07nT4TuBofzBrOx7uFtV2birr7qfBCsCoGV_ku9DHZLQ@mail.gmail.com> (raw)
In-Reply-To: <51ECDF5D.6010207@codesourcery.com>
On Mon, Jul 22, 2013 at 3:29 PM, Yao Qi <yao@codesourcery.com> wrote:
> On 07/22/2013 02:38 PM, Jan Kratochvil wrote:
>>
>> But the OS dependent part seems to be missing there:
>> arm-tdep.h:
>> /* Parse swi insn args, sycall record. */
>> int (*arm_swi_record) (struct regcache *regcache);
>> - which does not seem to be set anywhere
>>
>
> I raised this question during the code review, and Oza (the author) wanted
> to do them in phase 3, which handles OS related stuff, such as syscall.
> What we have in trunk is phase 2.
>
>
>> So the current set_gdbarch_process_record initialization could be possibly
>> moved to arm-tdep.c. But I did not play more with it.
>
>
> Right, the existing Oza's work in trunk is about ARM reversed debugging,
> without OS stuff. Probably we should call set_gdbarch_process_record in
> arm-tdep.c, but not sure how good or bad the results are.
I think you should call it arm process record but not reverse debug.
Reverse debug depend on the target support but I don't think call prec
as reverse debug is right.
Thanks,
Hui
>
> --
> Yao (齐尧)
next prev parent reply other threads:[~2013-07-22 7:34 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 [this message]
2013-07-22 7:26 ` Hui Zhu
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=CANFwon07nT4TuBofzBrOx7uFtV2birr7qfBCsCoGV_ku9DHZLQ@mail.gmail.com \
--to=teawater@gmail.com \
--cc=flameroc@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=yao@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