public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14391] gdb.Breakpoint.stop calling gdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail)
Date: Tue, 31 Jul 2012 19:18:00 -0000 [thread overview]
Message-ID: <bug-14391-4717-xt1n9RMb9c@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14391-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14391
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-07-31 19:18:16 UTC ---
This stack trace shows an exception being re-thrown.
It would be interesting to see where the exception was
originally thrown.
This might be a little difficult to dig up, though.
It would also be nice to see the exception being thrown.
Maybe this would let us find the thrower.
Another thing that would be worth knowing is which sniffer
is being called in frame_unwind_find_by_frame.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-07-31 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 14:22 [Bug python/14391] New: " kevin.pouget at gmail dot com
2012-07-31 19:18 ` tromey at redhat dot com [this message]
2012-08-02 13:38 ` [Bug python/14391] " tromey 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-14391-4717-xt1n9RMb9c@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).