public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug python/18445] New: shouldn't divulge implementation details in memory error messages from pretty printers
@ 2015-05-21 20:27 dje at google dot com
2023-08-31 13:54 ` [Bug python/18445] " tromey at sourceware dot org
0 siblings, 1 reply; 2+ messages in thread
From: dje at google dot com @ 2015-05-21 20:27 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug python/18445] shouldn't divulge implementation details in memory error messages from pretty printers
2015-05-21 20:27 [Bug python/18445] New: shouldn't divulge implementation details in memory error messages from pretty printers dje at google dot com
@ 2023-08-31 13:54 ` tromey at sourceware dot org
0 siblings, 0 replies; 2+ messages in thread
From: tromey at sourceware dot org @ 2023-08-31 13:54 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-08-31 13:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-21 20:27 [Bug python/18445] New: shouldn't divulge implementation details in memory error messages from pretty printers dje at google dot com
2023-08-31 13:54 ` [Bug python/18445] " tromey at sourceware dot org
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).