public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "i at ztrix dot me" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/16392] New: info prog after failure to insert breakpoint can cause gdb crash
Date: Sat, 04 Jan 2014 16:14:00 -0000 [thread overview]
Message-ID: <bug-16392-4717@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2014-01-04 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 16:14 i at ztrix dot me [this message]
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
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-16392-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).