[Bug gdb/26867] New: FAIL: gdb.threads/signal-sigtrap.exp: sigtrap thread 1: signal SIGTRAP reaches handler

[Bug gdb/26867] New: FAIL: gdb.threads/signal-sigtrap.exp: sigtrap thread 1: signal SIGTRAP reaches handler

[vries at gcc dot gnu.org]

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

            Bug ID: 26867
           Summary: FAIL: gdb.threads/signal-sigtrap.exp: sigtrap thread
                    1: signal SIGTRAP reaches handler
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I ran into this FAIL:
...
(gdb) PASS: gdb.threads/signal-sigtrap.exp: sigtrap thread 1: switch to sigtrap
thread
signal SIGTRAP^M
Continuing with signal SIGTRAP.^M
^M
Thread 1 "signal-sigtrap" received signal SIGTRAP, Trace/breakpoint trap.^M
0x00007ffff7fabc2a in pthread_create@@GLIBC_2.2.5 () from
/lib64/libpthread.so.0^M
(gdb) FAIL: gdb.threads/signal-sigtrap.exp: sigtrap thread 1: signal SIGTRAP
reaches handler
...

I managed to reproduce it on the command line, like once every couple of tries.

This is on openSUSE Tumbleweed, with glibc 2.32.

I tried the same on openSUSE Leap 15.2 with glibc 2.26, but it doesn't
reproduce there.

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

[Bug gdb/26867] FAIL: gdb.threads/signal-sigtrap.exp: sigtrap thread 1: signal SIGTRAP reaches handler

[vries at gcc dot gnu.org]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> I managed to reproduce it on the command line, like once every couple of
> tries.
> 

To be more specific, in conjunction with stress -c 5 on a dual-core/four-thread
cpu:
...
$ for n in $(seq 1 10); do echo -n "$n: "; gdb -batch
./outputs/gdb.threads/signal-sigtrap/signal-sigtrap -ex "break thread_function"
-ex run -ex "info threads" -ex "break sigtrap_handler" -ex "thread 1" -ex
"signal SIGTRAP" 2>&1 | egrep "hit Breakpoint 2| received signal"; done
1: Thread 1 "signal-sigtrap" received signal SIGTRAP, Trace/breakpoint trap.
2: Thread 1 "signal-sigtrap" received signal SIGTRAP, Trace/breakpoint trap.
3: Thread 1 "signal-sigtrap" hit Breakpoint 2, sigtrap_handler (sig=5) at
/data/gdb_versions/devel/src/gdb/testsuite/gdb.threads/signal-sigtrap.c:26
4: Thread 1 "signal-sigtrap" hit Breakpoint 2, sigtrap_handler (sig=5) at
/data/gdb_versions/devel/src/gdb/testsuite/gdb.threads/signal-sigtrap.c:26
5: Thread 1 "signal-sigtrap" hit Breakpoint 2, sigtrap_handler (sig=5) at
/data/gdb_versions/devel/src/gdb/testsuite/gdb.threads/signal-sigtrap.c:26
6: Thread 1 "signal-sigtrap" received signal SIGTRAP, Trace/breakpoint trap.
7: Thread 1 "signal-sigtrap" received signal SIGTRAP, Trace/breakpoint trap.
8: Thread 1 "signal-sigtrap" hit Breakpoint 2, sigtrap_handler (sig=5) at
/data/gdb_versions/devel/src/gdb/testsuite/gdb.threads/signal-sigtrap.c:26
9: Thread 1 "signal-sigtrap" hit Breakpoint 2, sigtrap_handler (sig=5) at
/data/gdb_versions/devel/src/gdb/testsuite/gdb.threads/signal-sigtrap.c:26
10: Thread 1 "signal-sigtrap" received signal SIGTRAP, Trace/breakpoint trap.
...

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

[Bug gdb/26867] FAIL: gdb.threads/signal-sigtrap.exp: sigtrap thread 1: signal SIGTRAP reaches handler

[vries at gcc dot gnu.org]

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
A very similar failure occurs here:
...
(gdb) PASS: gdb.threads/signal-command-handle-nopass.exp: step-over yes: thread
1 selected
signal SIGUSR1^M
Continuing with signal SIGUSR1.^M
^M
Thread 1 "signal-command-" received signal SIGUSR1, User defined signal 1.^M
0x00007ffff7fabc2a in pthread_create@@GLIBC_2.2.5 () from
/lib64/libpthread.so.0^M
(gdb) FAIL: gdb.threads/signal-command-handle-nopass.exp: step-over yes: signal
SIGUSR1
...

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