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/25234] Python pretty printer for C++ type fails when printing backtrace from a C function
Date: Sun, 05 Jun 2022 14:38:12 +0000	[thread overview]
Message-ID: <bug-25234-4717-oDhcx3kUhR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25234-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |tromey at sourceware dot org
         Resolution|---                         |FIXED

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Jonathan Wakely from comment #2)
> This seems to be fixed in GDB 10.1 (I can't test anything older).
> 
> I compiled the example with GCC 9.1 (which doesn't have the workaround in
> the libstdc++ printers) and don't get the IndexError exception now.

I thought there was a patch to temporarily change the current
language when printing a frame (assuming the language was "auto"
initially), but I can't easily find it now.

Anyway I am going to close this bug.

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

  parent reply	other threads:[~2022-06-05 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-25234-4717@http.sourceware.org/bugzilla/>
2022-02-03 13:11 ` jwakely.gcc at gmail dot com
2022-06-05 14:38 ` tromey at sourceware dot org [this message]
2022-06-05 14:38 ` 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-25234-4717-oDhcx3kUhR@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).