[Bug tdep/31839] New: [gdb/breakpoints, arm] Failure to set a hw wp while running disables hw wp permanently

[Bug tdep/31839] New: [gdb/breakpoints, arm] Failure to set a hw wp while running disables hw wp permanently

[vries at gcc dot gnu.org]

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

            Bug ID: 31839
           Summary: [gdb/breakpoints, arm] Failure to set a hw wp while
                    running disables hw wp permanently
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Arm variant of PR31837 - "[gdb/breakpoints, ppc64le] Failure to set a hw wp
while running disables hw wp permanently".

We can set a hardware watchpoint on arm when the current thread is stopped.

However, we cannot set one if it is running.

And once we tried and failed to because of that reason, we lose the ability to
set one, even if we stop the thread.

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

[Bug tdep/31839] [gdb/breakpoints, arm] Failure to set a hw wp while running disables hw wp permanently

[vries at gcc dot gnu.org]

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
I filed this PR separate from PR31705 because at the time I was not sure how to
fix that PR, but I saw an obvious fix for this one.

However, the proposed fix for PR31705 fixes this PR as well, so mark this a
duplicate.

*** This bug has been marked as a duplicate of bug 31705 ***

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