This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/14386] std::bitset not iterable
- From: "andreasheimberger at gmx dot at" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 01 Aug 2012 19:17:32 +0000
- Subject: [Bug python/14386] std::bitset not iterable
- Auto-submitted: auto-generated
- References: <bug-14386-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14386
--- Comment #5 from andreasheimberger at gmx dot at 2012-08-01 19:17:32 UTC ---
Sorry, I'm missing the routine in coding C. Just learned many languages, but
none of them perfect. There is still so much I have to learn. I tried to watch
varobj.c and found your line for the PyIter Check, but couldn't find the impl
of the error function, just think that i will cause an exception.
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.
The question that I have is more or less, why there is an implemented methode
for children. I thought this methode should be used to resolve the output for
-var-list-children and the to_string should resolve the object for the print
and -data-evaluate-expression of gdb.
But now I see that children is used to print the items, and appends them to the
to _string methode. 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...
Would be nice to have some workaround, but bitset is not iterable is the worst
output i can get, even the old is better.
Really appreciate your work. Made debugging much easier.
--
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.