public inbox for
help / color / mirror / Atom feed
From: "Franथईois Dumont" <>
Subject: [gcc r13-2967] libstdc++: [_GLIBCXX_INLINE_VERSION] Add gdb pretty print for _GLIBCXX_DEBUG
Date: Thu, 29 Sep 2022 18:42:50 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

commit r13-2967-g13337ea9a1ccffc7d73a8ff87f5f186fd4d0d51c
Author: François Dumont <>
Date:   Thu Sep 22 06:58:48 2022 +0200

    libstdc++: [_GLIBCXX_INLINE_VERSION] Add gdb pretty print for _GLIBCXX_DEBUG
    In _GLIBCXX_DEBUG mode containers are in std::__debug namespace but not template
    parameters. In _GLIBCXX_INLINE_VERSION mode most types are in std::__8 namespace but
    not std::__debug containers. We need to register specific type printers for this
            * python/libstdcxx/v6/ (add_one_template_type_printer): Register
            printer for types in std::__debug namespace with template parameters in std::__8

 libstdc++-v3/python/libstdcxx/v6/ | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/libstdc++-v3/python/libstdcxx/v6/ b/libstdc++-v3/python/libstdcxx/v6/
index 5a3dcbd13f9..245b6e3dbcd 100644
--- a/libstdc++-v3/python/libstdcxx/v6/
+++ b/libstdc++-v3/python/libstdcxx/v6/
@@ -2034,6 +2034,10 @@ def add_one_template_type_printer(obj, name, defargs):
         printer = TemplateTypePrinter(ns+name, defargs)
         gdb.types.register_type_printer(obj, printer)
+        # Add type printer for same type in debug namespace:
+        printer = TemplateTypePrinter('std::__debug::'+name, defargs)
+        gdb.types.register_type_printer(obj, printer)
 class FilteringTypePrinter(object):
     A type printer that uses typedef names for common template specializations.

                 reply	other threads:[~2022-09-29 18:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).