Bug 28468 - FAIL: gdb.threads/signal-command-handle-nopass.exp: step-over yes: signal SIGUSR1
Summary: FAIL: gdb.threads/signal-command-handle-nopass.exp: step-over yes: signal SIG...
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: threads (show other bugs)
Version: 11.1
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-18 16:33 UTC by Tom de Vries
Modified: 2021-10-18 16:33 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom de Vries 2021-10-18 16:33:18 UTC 
I'm seeing the following (OBS, tumbleweed, unix/m64, gcc-PIE installed):
...
(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
0x00007ffff7e43264 in pthread_create@GLIBC_2.2.5 () from /lib64/libc.so.6^M
(gdb) FAIL: gdb.threads/signal-command-handle-nopass.exp: step-over yes: signal SIGUSR1
...

In contrast, a passing case would show:
...
(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-" hit Breakpoint 3, handler (sig=10) at /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.threads/signal-command-handle-nopass.c:27^M
27      }^M
(gdb) PASS: gdb.threads/signal-command-handle-nopass.exp: step-over yes: signal SIGUSR1
...
Comment 1 Tom de Vries 2021-10-18 16:33:54 UTC 
[ Formerly reported here: PR 26867 comment 2. ]