Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,  <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4 3/6] Refactor arm_software_single_step to use regcache.
Date: Thu, 03 Dec 2015 14:37:00 -0000	[thread overview]
Message-ID: <861tb3tx7s.fsf@gmail.com> (raw)
In-Reply-To: <56603F64.6050906@ericsson.com> (Antoine Tremblay's message of	"Thu, 3 Dec 2015 08:11:00 -0500")

Antoine Tremblay <antoine.tremblay@ericsson.com> writes:

> Unfortunately we do for the syscall_next_pc target dependent call.
>
> The reason I did not change syscall_next_pc for regcache is that this
> would require the implementation of a syscall_next_pc that is not
> using the frame unwinders and directly inspects the stack for multiple
> targets.
>
> This would need to be done for arm,  mips, nios2, and tix6x.
>
> software_single_step would also have to be adapted for mips, nios2 and
> tix6x for this new api.

We don't need to touch targets other than arm.  syscall_next_pc is a
function pointer in struct gdbarch_tdep in arm-tdep.h.

/* Target-dependent structure in gdbarch.  */
struct gdbarch_tdep
{
  ...
  /* Return the expected next PC if FRAME is stopped at a syscall
     instruction.  */
  CORE_ADDR (*syscall_next_pc) (struct frame_info *frame);  
  ...
};

we can change frame to regcache.

The indentation looks odd in my mailer, if it is right to you, that is
fine.  Maybe, my mailer doesn't show the code format correctly.

-- 
Yao (齐尧)


  reply	other threads:[~2015-12-03 14:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 13:18 [PATCH v4 0/6] Support software single step and conditional breakpoints on ARM in GDBServer Antoine Tremblay
2015-12-02 13:18 ` [PATCH v4 6/6] Enable conditional breakpoints for targets that support software single step " Antoine Tremblay
2015-12-02 13:18 ` [PATCH v4 5/6] Enable software single stepping for while-stepping actions " Antoine Tremblay
2015-12-02 13:18 ` [PATCH v4 3/6] Refactor arm_software_single_step to use regcache Antoine Tremblay
2015-12-03 10:28   ` Yao Qi
2015-12-03 13:11     ` Antoine Tremblay
2015-12-03 14:37       ` Yao Qi [this message]
2015-12-03 14:41         ` Antoine Tremblay
2015-12-02 13:18 ` [PATCH v4 1/6] Replace breakpoint_reinsert_addr by get_next_pcs operation in GDBServer Antoine Tremblay
2015-12-02 13:18 ` [PATCH v4 2/6] Share some ARM target dependent code from GDB with GDBServer Antoine Tremblay
2015-12-02 13:19 ` [PATCH v4 4/6] Support software single step on ARM in GDBServer Antoine Tremblay
2015-12-03 11:17   ` Yao Qi
2015-12-03 13:58     ` Antoine Tremblay
2015-12-03 14:49       ` Yao Qi
2015-12-02 13:36 ` [PATCH v4 0/6] Support software single step and conditional breakpoints " Pedro Alves
2015-12-02 13:52   ` Antoine Tremblay

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=861tb3tx7s.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=antoine.tremblay@ericsson.com \
    --cc=gdb-patches@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