From: Pedro Alves <palves@redhat.com>
To: Craig Blackmore <craig.blackmore@embecosm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] RISC-V: enable have_nonsteppable_watchpoint by default
Date: Mon, 17 Sep 2018 12:54:00 -0000 [thread overview]
Message-ID: <539c4dcf-8bfa-b567-5112-42eac55645c8@redhat.com> (raw)
In-Reply-To: <c83e39fb-b1e8-cc67-85b5-c7cc66197078@embecosm.com>
On 09/16/2018 01:13 AM, Craig Blackmore wrote:
> The RISC-V debug spec 0.13 recommends that write triggers fire before
> the write is committed. If the target follows this behaviour, then
> have_nonsteppable_watchpoint needs to be set to 1 so that GDB will step
> over the watchpoint before checking if the value has changed.
>
> This patch adds a setshow for have_nonsteppable_watchpoint which defaults
> to 1 to match the recommended behaviour. If a target does not follow
> this timing, then 'set riscv have_nonsteppable_watchpoint 0' will need
> to be issued on the command line.
>
> gdb/ChangeLog:
>
> * riscv-tdep.c (set_have_nonsteppable_watchpoint): add
> callback for 'set riscv have_nonsteppable_watchpoint'
> (riscv_gdbarch_init): initialise gdbarch setting for
> have_nonesteppable_watchpoint
This is something the target/stub knows, right? I'd be much
better to make this automatic, so that users wouldn't have to
know to tweak anything.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-09-17 12:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 0:13 Craig Blackmore
2018-09-17 10:34 ` Andrew Burgess
2018-09-24 11:36 ` Craig Blackmore
2018-10-03 22:37 ` Joel Brobecker
2018-10-04 16:26 ` Craig Blackmore
2018-10-08 9:58 ` Andrew Burgess
2018-10-08 11:56 ` Pedro Alves
2018-10-08 14:25 ` Joel Brobecker
2018-10-08 14:37 ` Paul Koning
2018-10-08 14:42 ` Pedro Alves
2018-10-08 14:51 ` Joel Brobecker
2018-10-09 17:20 ` Craig Blackmore
2018-10-09 17:29 ` Paul Koning
2018-10-09 17:39 ` Pedro Alves
2018-10-23 10:34 ` Andrew Burgess
2018-10-08 14:50 ` Andreas Schwab
2018-09-17 12:54 ` Pedro Alves [this message]
2018-09-17 13:34 ` Andrew Burgess
2018-10-08 11:29 ` Pedro Alves
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=539c4dcf-8bfa-b567-5112-42eac55645c8@redhat.com \
--to=palves@redhat.com \
--cc=craig.blackmore@embecosm.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