This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug python/14386] std::bitset not iterable


http://sourceware.org/bugzilla/show_bug.cgi?id=14386

--- Comment #6 from Tom Tromey <tromey at redhat dot com> 2012-08-06 18:41:30 UTC ---
(In reply to comment #5)

> The thing is, that the message for -var-list-children is correct, because the
> returned value is not iterable. As much as i know bitset doesn't have an
> iterator.

This message does not refer to the bitset in your program, but rather to
a Python object created by the pretty-printer for the bitset.

> The question that I have is more or less, why there is an implemented methode
> for children.

This approach lets MI clients decide how many children to show (consider,
e.g., a vector of 1000 elements), and it lets the CLI apply various
"set print" settings, like "set print elements", to pretty-printed values.

> Is there a way to leave the output for the
> var-list-children methode as it was but using the new output for print and
> -data-eval...

MI clients can disable pretty-printing per-varobj.  See the manual for details.

> Would be nice to have some workaround, but bitset is not iterable is the worst
> output i can get, even the old is better.

If you encounter a pretty-printer bug you can bypass the Python code with
"print/r"

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]