Discussion:
[Bug gdb/23122] New: GDB hang after program received signal SIGUSR1 on FreeBSD
rajendra.sy at gmail dot com
2018-04-27 04:32:33 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23122

Bug ID: 23122
Summary: GDB hang after program received signal SIGUSR1 on
FreeBSD
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: rajendra.sy at gmail dot com
Target Milestone: ---

Test case: gdb.base/kill-after-signal

"next" command after singal
$ gdb gdb/testsuite/outputs/gdb.base/kill-after-signal/kill-after-signal
(gdb) b main
(gdb) handle SIGUSR1 stop print pass
(gdb) run
<breakpoint hit>
(gdb) continue
Continuing.

Program received signal SIGUSR1, User defined signal 1.
Python Exception <type 'exceptions.NameError'> Installation error:
gdb.execute_unwinders function is missing:
0x0000000800b0739a in thr_kill () from /lib/libc.so.7

Below commands after this hangs
1.
(gdb) next
Single stepping until exit from function thr_kill,
which has no line number information.
<hung>

2.
(gdb) stepi
<hung>

3.
(gdb) continue
Continuing.
<hung>
--
You are receiving this mail because:
You are on the CC list for the bug.
Loading...