public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/16470] Crash when inspecting STL containers with GDB pretty print
Date: Tue, 07 Jun 2022 15:36:32 +0000 [thread overview]
Message-ID: <bug-16470-4717-Ax8VltMYWA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16470-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16470
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
I tried this recently and was also unable to reproduce.
At the same time I don't really see why that assertion
should even be there. Either the value should automatically
un-lazy, or we could just explicitly un-lazy it at that point.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-07 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 12:51 [Bug python/16470] New: " aegges at web dot de
2014-01-21 8:41 ` [Bug python/16470] " marc.khouzam at ericsson dot com
2014-01-26 8:12 ` xhpohanka at gmail dot com
2014-01-26 9:28 ` qiyao at gcc dot gnu.org
2014-01-27 7:21 ` xhpohanka at gmail dot com
2014-01-27 8:31 ` qiyao at gcc dot gnu.org
2014-01-27 12:14 ` xhpohanka at gmail dot com
2021-09-15 7:02 ` beaux_monde at tut dot by
2022-06-07 15:36 ` tromey at sourceware dot org [this message]
2023-08-31 19:21 ` 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-16470-4717-Ax8VltMYWA@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).