[Bug symtab/15817] New: [i386] longjmp error in Python call catch_command_errors

[Bug symtab/15817] New: [i386] longjmp error in Python call catch_command_errors

[jan.kratochvil at redhat dot com]

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

            Bug ID: 15817
           Summary: [i386] longjmp error in Python call
                    catch_command_errors
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: jan.kratochvil at redhat dot com
              Host: i386-unknown-linux-gnu
            Target: i386-unknown-linux-gnu

Any recent i386 Fedora:

call catch_command_errors(execute_command, "python print 5", 0,
RETURN_MASK_ALL)
Warning:
Cannot insert breakpoint 0.
Error accessing memory address 0xa1900bbf: Input/output error.
0xf7f18d01 in longjmp (env=0x86f25a4, val=-1) at
../nptl/sysdeps/pthread/pt-longjmp.c:25
25      {
The program being debugged stopped while in a function called from GDB. 
Evaluation of the expression containing the function
(catch_command_errors) will be abandoned.
When the function is done executing, GDB will silently stop.
(gdb) FAIL: gdb.gdb/python-selftest.exp: call
catch_command_errors(execute_command, "python print 5", 0, RETURN_MASK_ALL)

Moreover occasionally:

call catch_command_errors(execute_command, "python print 5", 0,
RETURN_MASK_ALL)
infrun.c:5514: internal-error: insert_longjmp_resume_breakpoint: Assertion
`inferior_thread ()->control.exception_resume_breakpoint == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) FAIL: gdb.gdb/python-selftest.exp: call
catch_command_errors(execute_command, "python print 5", 0, RETURN_MASK_ALL)
(GDB internal error)

-- 
You are receiving this mail because:
You are on the CC list for the bug.