public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/18445] New: shouldn't divulge implementation details in memory error messages from pretty printers
Date: Thu, 21 May 2015 20:27:00 -0000	[thread overview]
Message-ID: <bug-18445-4717@http.sourceware.org/bugzilla/> (raw)

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.


             reply	other threads:[~2015-05-21 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 20:27 dje at google dot com [this message]
2023-08-31 13:54 ` [Bug python/18445] " tromey at sourceware dot org

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