[Bug python/18445] New: shouldn't divulge implementation details in memory error messages from pretty printers

[Bug python/18445] New: shouldn't divulge implementation details in memory error messages from pretty printers

[dje at google dot com]

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

            Bug ID: 18445
           Summary: shouldn't divulge implementation details in memory
                    error messages from pretty printers
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: minor
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com
  Target Milestone: ---

This pr is a corollary to PR 18438.

If the user prints an object with a pretty-printer that uses lazy strings,
s/he may get this error:
Cannot create a lazy string with address 0x0, and a non-zero length.

This may be confusing to the user. Lazy string? What's that?

OTOH the error text may be useful in other circumstances.
Should the pretty-printer machinery replace this text with something more
generic?
See print_stack_unless_memory_error.

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

[Bug python/18445] shouldn't divulge implementation details in memory error messages from pretty printers

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I think leaking the error is fine.
Pretty-printers should try to be robust, and when
they are buggy, the error and stack trace may be
a way to find what's wrong.  Also, gdb users are
normally programmers themselves, and won't be surprised
by this kind of error message.

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