[Bug c++/31342] New: Printer for std::string fails: Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.

[Bug c++/31342] New: Printer for std::string fails: Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.

[yuri at tsoft dot com]

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

            Bug ID: 31342
           Summary: Printer for std::string fails: Python Exception <class
                    'gdb.error'>: There is no member or method named
                    __short_mask.
           Product: gdb
           Version: 13.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: yuri at tsoft dot com
  Target Milestone: ---

When the user attempts to print an object of the type std::string - this fails:

> (gdb) p buildname
> $1 = Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.


gdb-13.2
FreeBSD 14.0-STABLE

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

[Bug c++/31342] Printer for std::string fails: Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
While there could be a gdb bug here, normally this sort of
thing should first be reported to whoever maintains the pretty-printers.
The code that is doing this lookup isn't part of gdb.
I'm going to guess it is part of libc++, since "short_mask" doesn't
seem to appear in libstdc++, but I am not actually sure.

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

[Bug c++/31342] Printer for std::string fails: Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.

[yuri at tsoft dot com]

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

--- Comment #2 from yuri at tsoft dot com ---
Who maintains pretty-printers?
Don't pretty-printers get shipped as part of gdb?

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

[Bug c++/31342] Printer for std::string fails: Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.

[tromey at sourceware dot org]

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

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to yuri from comment #2)
> Who maintains pretty-printers?
> Don't pretty-printers get shipped as part of gdb?

No, part of the design is that the printers themselves
are shipped alongside the code they work with. 

So, for example, the libstdc++ printers are all maintained
in the GCC source tree.  This way, if libstdc++ changes,
the printers can change at the same time, and gdb doesn't
need to be modified.

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

[Bug c++/31342] Printer for std::string fails: Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.

[yuri at tsoft dot com]

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

--- Comment #4 from yuri at tsoft dot com ---
The helpers actually come from this unmaintained project:
https://github.com/bsdjhb/libcxx-gdbpy

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

[Bug c++/31342] Printer for std::string fails: Python Exception <class 'gdb.error'>: There is no member or method named __short_mask.

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |MOVED

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
Yeah, any fix will probably have to be done there.

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