This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/16392] New: info prog after failure to insert breakpoint can cause gdb crash
- From: "i at ztrix dot me" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 04 Jan 2014 16:14:09 +0000
- Subject: [Bug breakpoints/16392] New: info prog after failure to insert breakpoint can cause gdb crash
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16392
Bug ID: 16392
Summary: info prog after failure to insert breakpoint can cause
gdb crash
Product: gdb
Version: 7.6
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: i at ztrix dot me
Below are the steps to reproduce this bug. And this is the discussion thread
about how we found this bug(Thanks to longld):
https://github.com/longld/peda/issues/21
:) ~ # gdb -n -q /bin/cat
Reading symbols from /usr/bin/cat...(no debugging symbols found)...done.
(gdb) tbreak *0xdeadbeef
Temporary breakpoint 1 at 0xdeadbeef
(gdb) r
Starting program: /bin/cat
warning: no loadable sections found in added symbol-file system-supplied DSO at
0x7ffff7ffa000
Warning:
Cannot insert breakpoint 1.
Error accessing memory address 0xdeadbeef: Input/output error.
(gdb) info prog
thread.c:615: internal-error: is_thread_state: Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
thread.c:615: internal-error: is_thread_state: Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted (core dumped)
--
You are receiving this mail because:
You are on the CC list for the bug.