public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at parcs dot ath.cx" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/18063] New: Buggy behavior after single-stepping into inferior's SIGWINCH handler
Date: Sat, 28 Feb 2015 15:39:00 -0000 [thread overview]
Message-ID: <bug-18063-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18063
Bug ID: 18063
Summary: Buggy behavior after single-stepping into inferior's
SIGWINCH handler
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: patrick at parcs dot ath.cx
GDB seems to malfunction after catching a SIGWINCH signal and stepping into the
program's SIGWINCH handler. In particular GDB seems to catch an endless stream
of SIGTRAPs when attempting to exit the SIGWINCH handler. This behavior can be
seen when debugging GDB with GDB:
$ gdb gdb
(gdb) catch signal SIGWINCH
Catchpoint 1 (signal SIGWINCH)
(gdb) run
Starting program: /scratchpad/binutils-gdb-build/gdb/gdb
(gdb) <resize terminal>
Catchpoint 1 (signal SIGWINCH), 0x00007ffff6d784f0 in poll () from
/lib/x86_64-linux-gnu/libc.so.6
(gdb) step
Single stepping until exit from function poll,
which has no line number information.
rl_sigwinch_handler (sig=28) at
/home/patrick/code/binutils-gdb/readline/signals.c:246
246 {
(gdb) next
259 RL_SETSTATE(RL_STATE_SIGHANDLER);
(gdb) finish
Run till exit from #0 rl_sigwinch_handler (sig=28) at
/home/patrick/code/binutils-gdb/readline/signals.c:246
Program received signal SIGTRAP, Trace/breakpoint trap.
rl_sigwinch_handler (sig=28) at
/home/patrick/code/binutils-gdb/readline/signals.c:260
260 rl_resize_terminal ();
(gdb) finish
Run till exit from #0 rl_sigwinch_handler (sig=28) at
/home/patrick/code/binutils-gdb/readline/signals.c:260
Program received signal SIGTRAP, Trace/breakpoint trap.
rl_resize_terminal () at
/home/patrick/code/binutils-gdb/readline/terminal.c:364
364 {
(gdb) <ad infinitum..>
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-02-28 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 15:39 patrick at parcs dot ath.cx [this message]
2015-02-28 16:01 ` [Bug breakpoints/18063] " palves at redhat dot com
2015-02-28 16:01 ` patrick at parcs dot ath.cx
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-18063-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).