[Bug threads/28065] New: FAIL: gdb.threads/access-mem-running-thread-exit.exp: all-stop: access mem (print global_var after writing again, inf=1, iter=354)

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

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

            Bug ID: 28065
           Summary: FAIL: gdb.threads/access-mem-running-thread-exit.exp:
                    all-stop: access mem (print global_var after writing
                    again, inf=1, iter=354)
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I did a build and test run of gdb-11-branch on openSUSE Tumbleweed (FTR, tested
using gcc 10.3.0 instead of the platform default gcc 11.1.1, which causes lots
of FAILs), and ran into:
...
(gdb) inferior 1^M
[Switching to inferior 1 [process 786] (access-mem-running-thread-exit)]^M
[Switching to thread 1.16106 (Thread 0x7fffcafdd640 (LWP 1066))](running)^M
(gdb) print global_var = 555^M
$1413 = 555^M
(gdb) print global_var^M
$1414 = 555^M
(gdb) print global_var = 333^M
$1415 = 333^M
(gdb) print global_var^M
Cannot access memory at address 0x404070^M
(gdb) FAIL: gdb.threads/access-mem-running-thread-exit.exp: all-stop: access
mem (print global_var after writing again, inf=1, iter=354)
...

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