[Bug mi/20385] New: Executing "info frame" with non-existing frame number crashes gdb

["korcankaraokcu at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 20385
           Summary: Executing "info frame" with non-existing frame number
                    crashes gdb
           Product: gdb
           Version: 7.11.1
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: korcankaraokcu at gmail dot com
  Target Milestone: ---

Executing "info frame 11" while the available frame numbers were between
0-10(as shown with "bt" command) gave the output below:

~"Stack frame at 0xb:\n"
~" rip = 0x0; saved rip = 0x0\n"
~" called by frame at 0x7ffe29cefed0\n"
~" Arglist at 0x7ffe29cefeb8, args: \n"
~" Locals at 0x7ffe29cefeb8, Previous frame's sp is 0x7ffe29cefec8\n"
~"value.c:3939: internal-error: value_fetch_lazy: Assertion `frame != NULL'
failed.\nA problem internal to GDB has been detected,\nfurther debugging may
prove unreliable.\nQuit this debugging session? "
~"(y or n) [answered Y; input not from terminal]\n"
&"\nThis is a bug, please report it."
&"  For instructions, see:\n<http://www.gnu.org/software/gdb/bugs/>."
&"\n\n"

I'm using Kubuntu 14.04 x86_64

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