[Bug testsuite/28478] New: FAIL: gdb.gdb/selftest.exp: backtrace through signal handler

[Bug testsuite/28478] New: FAIL: gdb.gdb/selftest.exp: backtrace through signal handler

[vries at gcc dot gnu.org]

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

            Bug ID: 28478
           Summary: FAIL: gdb.gdb/selftest.exp: backtrace through signal
                    handler
           Product: gdb
           Version: 11.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On OBS with distro openSUSE Tumbleweed and target board unix/-m32, I run into:
...
(gdb) PASS: gdb.gdb/selftest.exp: xgdb is at prompt
set prompt (xgdb) 
(xgdb) PASS: gdb.gdb/selftest.exp: Set xgdb_prompt

Thread 1 "xgdb" received signal SIGINT, Interrupt.
0x00007ffff755790f in write () from /lib64/libc.so.6
(gdb) PASS: gdb.gdb/selftest.exp: send ^C to child process
signal SIGINT
Continuing with signal SIGINT.
Quit
(xgdb) PASS: gdb.gdb/selftest.exp: send SIGINT signal to child process

Thread 1 "xgdb" received signal SIGINT, Interrupt.
0x00007ffff7fdacb1 in _dl_fixup () from /lib64/ld-linux-x86-64.so.2
(gdb) PASS: gdb.gdb/selftest.exp: send ^C to child process again
thread 1
[Switching to thread 1 (Thread 0x7ffff67da040 (LWP 7104))]
#0  0x00007ffff7fdacb1 in _dl_fixup () from /lib64/ld-linux-x86-64.so.2
(gdb) PASS: gdb.gdb/selftest.exp: thread 1
backtrace
#0  0x00007ffff7fdacb1 in _dl_fixup () from /lib64/ld-linux-x86-64.so.2
#1  0x00007ffff7fe263e in _dl_runtime_resolve_xsavec () from
/lib64/ld-linux-x86-64.so.2
#2  0x00005555556daee8 in start_event_loop () at ../../gdb/main.c:449
#3  captured_command_loop () at ../../gdb/main.c:481
#4  0x0000555555d0fa25 in captured_main(void*) [clone .constprop.0]
(data=data@entry=0x7fffffffd4e0) at ../../gdb/main.c:1358
#5  0x00005555556f109d in gdb_main (args=0x7fffffffd4e0) at
../../gdb/main.c:1369
#6  main (argc=<optimized out>, argv=<optimized out>) at ../../gdb/gdb.c:32
(gdb) FAIL: gdb.gdb/selftest.exp: backtrace through signal handler
...

In the passing case, we'd already be in poll at the first SIGINT, but instead
we're in write.

Then after the second SIGINT, we're in _dl_fixup, but expect to be in poll.

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