[Bug gdb/30542] New: [gdb] PASS: gdb.base/watch-before-fork.exp: test: continue to watchpoint

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 30542
           Summary: [gdb] PASS: gdb.base/watch-before-fork.exp: test:
                    continue to watchpoint
           Product: gdb
           Version: 13.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With a gdb 13.2 based package, on openSUSE Leap 15.4 powerpc64le, I run into:
...
(gdb) PASS: gdb.base/watch-before-fork.exp: test: continue to watchpoint
continue^M
Continuing.^M
[Detaching after fork from child process 19572]^M
^M
Hardware access (read/write) watchpoint 2: global_var^M
^M
Value = 1^M
0x00000001000007d0 in __do_global_dtors_aux ()^M
(gdb) FAIL: gdb.base/watch-before-fork.exp: test: continue to catch fork
...

One curious thing about the test-case is that it doesn't exercise the scenario
listed in the PR and indeed, the commit message: it doesn't do "catch fork".

However, if I checkout the commit and run the test, it passes, and when I
revert the fix, it fails, so the test-case does function as a regression test
for the fix.

Anyway, I can't think of a reason why __do_global_dtors_aux should be accessing
global_var, so for now I'm classifying as component gdb rather than testsuite.

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