[Bug gdb/29865] New: The GDB dies during unwind the stack - question

["filip.bascarevic at siemens dot com" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 29865
           Summary: The GDB dies during unwind the stack - question
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: filip.bascarevic at siemens dot com
  Target Milestone: ---

Hello community,
I was debugging something and my GDB application just died when I wanted to do
"backtrace". After debugging the source code, I figure out the application died
at the assert in the file gdb/dwarf2/loc.c:1147 (in the function
dwarf_expr_reg_to_entry_parameter()). The reason why the assert is triggered is
because I setup the backtrace limit to 30 and during unwinding the stack the
frame type was "INLINE_FRAME" so the get_priv_frame() function returned NULL
(see line gdb/frame.c:2527) and the assert is triggered. 
Is it really necessary to have this assert? Why we need to consider if the
current frame is "INLINE_FRAME" on this place? 

Problematic code is:
    while (get_frame_type (frame) == INLINE_FRAME)
    {
      frame = get_prev_frame (frame);
      gdb_assert (frame != NULL);
    }

Thanks a lot for the support,
Filip Bascarevic

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