From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id EA65A38367BC; Wed,  7 Dec 2022 15:24:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EA65A38367BC
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1670426667;
	bh=geAK32INiI2d/1xu5M4mq27Vn8aoWCetlujzEV5aOx4=;
	h=From:To:Subject:Date:From;
	b=SjF7FoS3YRfKfr98ZJUfIbE8mNui93lv2zGleU3eSMrwLsZ7s4X785bN8HlpWwRtO
	 GPYkeOtDG0dZH2du+iBFLKts1OH3UiJdn3nJUSSpc5frGeGPQUXksyKl9rl+mnIVy6
	 idje2TaadKiuHua1ir1DyEHCn/lFtYI02aTkYcyY=
From: "filip.bascarevic at siemens dot com"
 <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29865] New: The GDB dies during unwind the stack - question
Date: Wed, 07 Dec 2022 15:24:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: filip.bascarevic at siemens dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-29865-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

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

            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 triggere=
d 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.=20
Is it really necessary to have this assert? Why we need to consider if the
current frame is "INLINE_FRAME" on this place?=20

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

Thanks a lot for the support,
Filip Bascarevic

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