public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug breakpoints/16392] New: info prog after failure to insert breakpoint can cause gdb crash
@ 2014-01-04 16:14 i at ztrix dot me
2014-01-04 16:16 ` [Bug breakpoints/16392] " i at ztrix dot me
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: i at ztrix dot me @ 2014-01-04 16:14 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug breakpoints/16392] info prog after failure to insert breakpoint can cause gdb crash
2014-01-04 16:14 [Bug breakpoints/16392] New: info prog after failure to insert breakpoint can cause gdb crash i at ztrix dot me
@ 2014-01-04 16:16 ` i at ztrix dot me
2014-01-21 22:40 ` sergiodj at redhat dot com
2014-01-21 22:42 ` sergiodj at redhat dot com
2 siblings, 0 replies; 4+ messages in thread
From: i at ztrix dot me @ 2014-01-04 16:16 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=16392
--- Comment #1 from zTrix <i at ztrix dot me> ---
We have tested it on gdb 7.6.2(Archlinux x86-64), and gdb 7.4(Maybe Ubuntu I
think). Both produce this same output.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug breakpoints/16392] info prog after failure to insert breakpoint can cause gdb crash
2014-01-04 16:14 [Bug breakpoints/16392] New: info prog after failure to insert breakpoint can cause gdb crash i at ztrix dot me
2014-01-04 16:16 ` [Bug breakpoints/16392] " i at ztrix dot me
@ 2014-01-21 22:40 ` sergiodj at redhat dot com
2014-01-21 22:42 ` sergiodj at redhat dot com
2 siblings, 0 replies; 4+ messages in thread
From: sergiodj at redhat dot com @ 2014-01-21 22:40 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=16392
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |sergiodj at redhat dot com
--- Comment #2 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
Proposed patch: <https://sourceware.org/ml/gdb-patches/2014-01/msg00709.html>
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug breakpoints/16392] info prog after failure to insert breakpoint can cause gdb crash
2014-01-04 16:14 [Bug breakpoints/16392] New: info prog after failure to insert breakpoint can cause gdb crash i at ztrix dot me
2014-01-04 16:16 ` [Bug breakpoints/16392] " i at ztrix dot me
2014-01-21 22:40 ` sergiodj at redhat dot com
@ 2014-01-21 22:42 ` sergiodj at redhat dot com
2 siblings, 0 replies; 4+ messages in thread
From: sergiodj at redhat dot com @ 2014-01-21 22:42 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=16392
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at sourceware dot org |sergiodj at redhat dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-01-21 22:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-04 16:14 [Bug breakpoints/16392] New: info prog after failure to insert breakpoint can cause gdb crash i at ztrix dot me
2014-01-04 16:16 ` [Bug breakpoints/16392] " i at ztrix dot me
2014-01-21 22:40 ` sergiodj at redhat dot com
2014-01-21 22:42 ` sergiodj at redhat dot com
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).