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 E54F13834410; Tue,  2 Feb 2021 14:37:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E54F13834410
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/27315] Walking threads during frame display
 pretty-printer causes crashes
Date: Tue, 02 Feb 2021 14:37:33 +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: 10.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
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: 
Message-ID: <bug-27315-4717-1wv9ICNePe@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27315-4717@http.sourceware.org/bugzilla/>
References: <bug-27315-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: Tue, 02 Feb 2021 14:37:34 -0000

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

--- Comment #3 from Simon Marchi <simark at simark dot ca> ---
What I get from this is that we are iterating on the frames, updating the
thread list throws the frame cache away, here:

#0  reinit_frame_cache () at /home/simark/src/binutils-gdb/gdb/frame.c:2042
#1  0x000055555e4a7b38 in switch_to_no_thread () at
/home/simark/src/binutils-gdb/gdb/thread.c:1334
#2  0x000055555d2bec61 in switch_to_inferior_no_thread (inf=3D0x61500002010=
0) at
/home/simark/src/binutils-gdb/gdb/inferior.c:628
#3  0x000055555e49d589 in prune_threads () at
/home/simark/src/binutils-gdb/gdb/thread.c:728
#4  0x000055555d51bbd0 in thread_db_target::update_thread_list
(this=3D0x555565a0f940 <the_thread_db_target>) at
/home/simark/src/binutils-gdb/gdb/linux-thread-db.c:1606
#5  0x000055555e451a93 in target_update_thread_list () at
/home/simark/src/binutils-gdb/gdb/target.c:3141
#6  0x000055555e4b0f85 in update_thread_list () at
/home/simark/src/binutils-gdb/gdb/thread.c:2038
#7  0x000055555db4e8d2 in infpy_threads (self=3D0x7fffeea55ae0, args=3D0x0)=
 at
/home/simark/src/binutils-gdb/gdb/python/py-inferior.c:397


So we end up using a frame object that has been freed.

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