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 C1EF73858436; Mon,  7 Feb 2022 17:51:38 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C1EF73858436
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/28856] Python pretty printer causes stack overflow when
 printing frame arguments
Date: Mon, 07 Feb 2022 17:51:38 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: python
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: blarsen at redhat 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: cc
Message-ID: <bug-28856-4717-UT4WM3wpep@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28856-4717@http.sourceware.org/bugzilla/>
References: <bug-28856-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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2022 17:51:38 -0000

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

B. Larsen <blarsen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |blarsen at redhat dot com

--- Comment #6 from B. Larsen <blarsen at redhat dot com> ---
I have managed to reproduce the crash without using the pretty printer. In
fact, all I need to reproduce is:

gdb -q ec -ex start -ex n -ex s -ex bt

and it crashes using backtrace, up or finish. What I found while trying to
debug this is that there is a corruption in the linked list, creating the
following entry:

1: *this_frame =3D {level =3D 0, pspace =3D 0x0, aspace =3D 0x26b6d00, prol=
ogue_cache =3D
0x0, unwind =3D 0x0, prev_arch =3D {p =3D false, arch =3D 0x0}, prev_pc =3D=
 {status =3D
CC_UNKNOWN, masked =3D false, value =3D 0x0}, prev_func =3D {addr =3D 0x401=
13c, status
=3D CC_VALUE}, this_id =3D {p =3D frame_id_status::COMPUTED, value =3D {sta=
ck_addr =3D
0x0, code_addr =3D 0x0, special_addr =3D 0x0, stack_status =3D FID_STACK_SE=
NTINEL,
code_addr_p =3D 0, special_addr_p =3D 1, artificial_depth =3D 0}}, base =3D=
 0x0,
base_cache =3D 0x0, next =3D 0x288fee0, prev_p =3D true, prev =3D 0x288ffb0,
stop_reason =3D UNWIND_NO_REASON, stop_string =3D 0x0}

(top-gdb) p this_frame
$2 =3D (frame_info *) 0x288fee0

I haven't tracked down where this is happening, but my guess is somewhere
during the step process.

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