public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "kevin.pouget at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/14391] New: gdb.Breakpoint.stop calling gdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail) Date: Tue, 24 Jul 2012 14:22:00 -0000 [thread overview] Message-ID: <bug-14391-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14391 Bug #: 14391 Summary: gdb.Breakpoint.stop calling gdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail) Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: python AssignedTo: unassigned@sourceware.org ReportedBy: kevin.pouget@gmail.com Classification: Unclassified Created attachment 6552 --> http://sourceware.org/bugzilla/attachment.cgi?id=6552 Backtrace of the failing assertion In gdb.Breakpoint.stop callback, the script reads a register value with gdb.parse_and_eval("(int) $rax"). The callback always returns False, so GDB never actually gives the control back to the CLI. Sometimes (certainly a matter of timing), when I hit Ctrl^C, GDB crashes (a failing assertion) with the backtrace in the attachment. There is no other problem with the script. -- 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 reply other threads:[~2012-07-24 14:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-24 14:22 kevin.pouget at gmail dot com [this message] 2012-07-31 19:18 ` [Bug python/14391] " tromey at redhat dot com 2012-08-02 13:38 ` 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@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: linkBe 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).