This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug mi/11335] -var-evaluate-expression should return the pretty printer's to_string result
- From: "krf at gmx dot de" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 05 Feb 2014 00:14:17 +0000
- Subject: [Bug mi/11335] -var-evaluate-expression should return the pretty printer's to_string result
- Auto-submitted: auto-generated
- References: <bug-11335-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=11335
Kevin Funk <krf at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |krf at gmx dot de
--- Comment #5 from Kevin Funk <krf at gmx dot de> ---
Hey Vladimir.
I'm curious if this issue has been solved in one or the other way up to now. I
was wondering if we could resolve those '{...}' for non-simple types in
KDevelop's GDB support, and stumbled upon this bug entry.
I think it's valid request to get some 'short summary' of non-simple types.
Containers are the best example, it'd be good to know how many items they
contain, without requesting the individual child items.
Given the documentation about the pretty printer's to_string() method:
"When printing from the CLI, if the to_string method exists, then gdb will
prepend its result to the values returned by children. Exactly how this
formatting is done is dependent on the display hint, and may change as more
hints are added. Also, depending on the print settings (see Print Settings),
the CLI may print just the result of to_string in a stack trace, omitting the
result of children."
=> Here, to_string() is used unconditionally, children() is optional. Can't we
transfer that kind of behavior to -var-evaluate-expression and friends as well?
--
You are receiving this mail because:
You are on the CC list for the bug.