[Bug remote/17700] New: failed assertion in findvar.c -- frame_id_p ( get_frame_id (frame) )

["schulte.eric at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17700

            Bug ID: 17700
           Summary: failed assertion in findvar.c -- frame_id_p (
                    get_frame_id (frame) )
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: normal
          Priority: P2
         Component: remote
          Assignee: unassigned at sourceware dot org
          Reporter: schulte.eric at gmail dot com

Created attachment 8005
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8005&action=edit
ARM binary executable, tinyhttpd web server

The following text is printed by GDB when executing stepi in a while loop using
a gdb script.

    0xf67e3020 in ?? ()
    1: x/i $pc
    findvar.c:292: internal-error: value_of_register_lazy: Assertion
`frame_id_p (get_frame_id (frame))' failed.
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    Quit this debugging session? (y or n) [answered Y; input not from terminal]

    This is a bug, please report it.  For instructions, see:
    <http://www.gnu.org/software/gdb/bugs/>.

    findvar.c:292: internal-error: value_of_register_lazy: Assertion
`frame_id_p (get_frame_id (frame))' failed.
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    Create a core file of GDB? (y or n) [answered Y; input not from terminal]

The setup is an ARM binary run using qemu-arm-static user emulation.

    qemu-arm-static -g 1234 ./httpd 8888

The -g option to qemu starts a gdb stub which is first connected to, before
setting a breakpoint, continuing, and then executing a long series of stepi
instructions before the bug is exercised.  I'll attach the binary in case it is
of any use.  Note: if you try to run this and get as far as actually running
the executable, you'll have to actually submit a request to the server (e.g.,
with curl) to exercise the bug.

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