public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andreasheimberger at gmx dot at" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14386] std::bitset not iterable
Date: Wed, 01 Aug 2012 19:17:00 -0000	[thread overview]
Message-ID: <bug-14386-4717-wgeyGYy75I@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <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.


  parent reply	other threads:[~2012-08-01 19:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  8:02 [Bug python/14386] New: " andreasheimberger at gmx dot at
2012-07-31 16:00 ` [Bug python/14386] " tromey at redhat dot com
2012-07-31 21:27 ` andreasheimberger at gmx dot at
2012-08-01 16:02 ` tromey at redhat dot com
2012-08-01 16:21 ` tromey at redhat dot com
2012-08-01 16:30 ` tromey at redhat dot com
2012-08-01 19:17 ` andreasheimberger at gmx dot at [this message]
2012-08-06 18:41 ` tromey at redhat dot com
2012-08-06 18:45 ` cvs-commit at gcc dot gnu.org
2012-08-06 18:45 ` tromey at redhat dot com
2012-08-06 18:45 ` cvs-commit at gcc dot gnu.org
2012-08-16 17:09 ` cvs-commit at gcc dot gnu.org
2012-08-16 17:10 ` tromey at redhat 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-14386-4717-wgeyGYy75I@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).