public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/16286] value.string(length = x) broken for common variable length arrays idiom
Date: Tue, 03 Dec 2013 14:35:00 -0000 [thread overview]
Message-ID: <bug-16286-4717-jrNbqn8WiT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16286-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16286
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #7 from Tom Tromey <tromey at redhat dot com> ---
(In reply to dje from comment #4)
> I recognize the problem, but error checking and clipping of the length needs
> to be done in python before invoking value.string().
I'd rather we not advise users to do this.
Instead gdb should do the throttling.
lazy_string is intended to help with this problem;
also perhaps some other fix is possible in the value printing code.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-12-03 14:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 22:47 [Bug python/16286] New: " dje at google dot com
2013-12-02 22:47 ` [Bug python/16286] " dje at google dot com
2013-12-02 23:33 ` dje at google dot com
2013-12-03 1:52 ` asmwarrior at gmail dot com
2013-12-03 2:48 ` brobecker at gnat dot com
2013-12-03 5:16 ` dje at google dot com
2013-12-03 5:20 ` dje at google dot com
2013-12-03 5:23 ` dje at google dot com
2013-12-03 14:35 ` tromey at redhat dot com [this message]
2013-12-03 23:30 ` dje at google dot com
2013-12-04 2:29 ` brobecker at adacore dot com
2013-12-04 4:13 ` dje at google dot com
2013-12-11 0:21 ` cvs-commit at gcc dot gnu.org
2013-12-11 0:26 ` dje at google dot com
2013-12-11 9:14 ` brobecker at adacore dot com
2013-12-11 15:25 ` tromey at redhat dot com
2013-12-13 16:52 ` cvs-commit at gcc dot gnu.org
2013-12-19 15:53 ` brobecker at gnat dot com
2013-12-19 16:27 ` xdje42 at gmail dot com
2013-12-19 16:30 ` xdje42 at gmail dot com
2013-12-19 18:03 ` brobecker at adacore 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-16286-4717-jrNbqn8WiT@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).