[Bug python/14391] New: gdb.Breakpoint.stop calling gdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail)

[Bug python/14391] New: gdb.Breakpoint.stop calling gdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail)

[kevin.pouget at gmail dot com]

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.

[Bug python/14391] gdb.Breakpoint.stop calling gdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail)

[tromey at redhat dot com]

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.

[Bug python/14391] gdb.Breakpoint.stop calling gdb.parse_and_eval("(int) $rax") + Ctrl^C crashes GDB (assertion fail)

[tromey at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=14391

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-08-02 13:37:49 UTC ---
This turns out to be a duplicate.

*** This bug has been marked as a duplicate of bug 14100 ***

-- 
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.