This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/14391] New: gdb.Breakpoint.stop callinggdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail)
- From: "kevin.pouget at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 24 Jul 2012 14:22:07 +0000
- Subject: [Bug python/14391] New: gdb.Breakpoint.stop callinggdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail)
- Auto-submitted: auto-generated
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.