Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Terry Guo <flameroc@gmail.com>
Cc: Hui Zhu <teawater@gmail.com>, gdb@sourceware.org
Subject: Re: Reverse debugging for arm baremetal targets?
Date: Mon, 22 Jul 2013 06:38:00 -0000	[thread overview]
Message-ID: <20130722063842.GA24373@host2.jankratochvil.net> (raw)
In-Reply-To: <CAGbRaL4_DQ9fYXX8pj6x8rwXbMBsS7ZCi2D2jj_hSSvv-iZfdA@mail.gmail.com>

On Mon, 22 Jul 2013 08:10:33 +0200, Terry Guo wrote:
> Thanks for your reply. I did some tests and it seems to me that
> reverse debugging doesn't work for baremetal targets.

It looks so:

$ grep '  set_gdbarch_process_record ' gdb/*
amd64-linux-tdep.c:  set_gdbarch_process_record (gdbarch, i386_process_record);
arm-linux-tdep.c:  set_gdbarch_process_record (gdbarch, arm_process_record);
i386-linux-tdep.c:  set_gdbarch_process_record (gdbarch, i386_process_record);
moxie-tdep.c:  set_gdbarch_process_record (gdbarch, moxie_process_record);

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
 
So the current set_gdbarch_process_record initialization could be possibly
moved to arm-tdep.c.  But I did not play more with it.


Jan


  reply	other threads:[~2013-07-22  6:38 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 [this message]
2013-07-22  7:30       ` Yao Qi
2013-07-22  7:34         ` Hui Zhu
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=20130722063842.GA24373@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=flameroc@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=teawater@gmail.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