public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/26619] [arm] Unexpected error setting breakpoint/watchpoint
Date: Tue, 23 Apr 2024 07:39:37 +0000	[thread overview]
Message-ID: <bug-26619-4717-8Q9JKEL2Ts@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26619-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26619

--- Comment #4 from Luis Machado <luis.machado at arm dot com> ---
I think this used to be the case on older kernels. One of the fixes was to
actually try to insert the hardware watchpoint (say, on PC), and see if that
succeeds. If so, then go ahead and use it. Otherwise, assume it doesn't work.

If this isn't manifesting anymore, maybe we should just close it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-23  7:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 15:13 [Bug breakpoints/26619] New: " vries at gcc dot gnu.org
2020-09-15 15:14 ` [Bug breakpoints/26619] " vries at gcc dot gnu.org
2020-09-15 15:32 ` luis.machado at linaro dot org
2020-09-16  7:11 ` vries at gcc dot gnu.org
2024-04-23  0:58 ` thiago.bauermann at linaro dot org
2024-04-23  7:39 ` luis.machado at arm dot com [this message]
2024-04-23 18:44 ` thiago.bauermann at linaro dot org
2024-04-24  0:13 ` thiago.bauermann at linaro dot org
2024-04-24 17:47 ` thiago.bauermann at linaro dot org
2024-04-24 21:11 ` vries at gcc dot gnu.org
2024-04-25 13:59 ` vries at gcc dot gnu.org

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=bug-26619-4717-8Q9JKEL2Ts@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).