public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/30556] printing the std::string array fails: {Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.
Date: Thu, 03 Aug 2023 19:20:40 +0000	[thread overview]
Message-ID: <bug-30556-4717-N1LlvDTH5r@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30556-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simon.marchi at polymtl dot ca

--- Comment #8 from Simon Marchi <simon.marchi at polymtl dot ca> ---
(In reply to yuri from comment #7)
> So gdb does refer to '__short_mask' in the file
> /usr/local/share/libcxx-gdbpy/libcxx/printers.py that it installs.

That file is installed (and maintained) by libcxx:

https://github.com/llvm-mirror/libcxx/blob/master/utils/gdb/libcxx/printers.py

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

  parent reply	other threads:[~2023-08-03 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 17:45 [Bug c++/30556] New: " yuri at tsoft dot com
2023-06-16 14:25 ` [Bug c++/30556] " tromey at sourceware dot org
2023-08-03 16:44 ` tromey at sourceware dot org
2023-08-03 16:50 ` yuri at tsoft dot com
2023-08-03 18:34 ` tromey at sourceware dot org
2023-08-03 18:42 ` yuri at tsoft dot com
2023-08-03 18:43 ` yuri at tsoft dot com
2023-08-03 18:44 ` yuri at tsoft dot com
2023-08-03 18:46 ` yuri at tsoft dot com
2023-08-03 19:20 ` simon.marchi at polymtl dot ca [this message]
2023-08-03 20:37 ` yuri at tsoft dot com
2023-08-03 20:39 ` yuri at tsoft dot com
2023-08-03 22:01 ` yuri at tsoft dot com

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-30556-4717-N1LlvDTH5r@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).