public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-27315-4717-1wv9ICNePe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27315-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27315
--- 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=0x615000020100) 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=0x555565a0f940 <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=0x7fffeea55ae0, args=0x0) at
/home/simark/src/binutils-gdb/gdb/python/py-inferior.c:397
So we end up using a frame object that has been freed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-02 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 13:40 [Bug python/27315] New: " psmith at gnu dot org
2021-02-02 13:40 ` [Bug python/27315] " psmith at gnu dot org
2021-02-02 14:29 ` simark at simark dot ca
2021-02-02 14:37 ` simark at simark dot ca [this message]
2022-02-21 1:34 ` psmith at gnu dot org
2023-08-01 18:18 ` tromey at sourceware dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27315-4717-1wv9ICNePe@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).