This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/18062] New: Infinite loop when single-step out of syscall
- From: "patrick at parcs dot ath.cx" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 28 Feb 2015 15:23:03 +0000
- Subject: [Bug breakpoints/18062] New: Infinite loop when single-step out of syscall
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18062
Bug ID: 18062
Summary: Infinite loop when single-step out of syscall
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
When the inferior is stopped inside a syscall (e.g. poll), single-stepping out
of this syscall (via "step") causes GDB to loop and to slowly consume more and
more memory. This can easily be seen when debugging GDB with GDB:
$ gdb gdb
(gdb) run
Starting program: /scratchpad/binutils-gdb-build/gdb/gdb
(gdb) ^C
Program received signal SIGINT, Interrupt.
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.
<infinite loop here>
--
You are receiving this mail because:
You are on the CC list for the bug.