public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mail at milianw dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/13419] New: Unable to pretty-print map of lists Date: Sun, 20 Nov 2011 22:42:00 -0000 [thread overview] Message-ID: <bug-13419-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13419 Bug #: 13419 Summary: Unable to pretty-print map of lists Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: mi AssignedTo: unassigned@sourceware.org ReportedBy: mail@milianw.de Classification: Unclassified See also: https://bugs.kde.org/show_bug.cgi?id=257834 Compile the following code: ~~~~~~~~~~ #include <map> #include <list> #include <string> using namespace std; int main() { typedef map<string, list<string> > map_t; map_t m; m["one"].push_back("a"); m["one"].push_back("b"); m["one"].push_back("c"); m["two"].push_back("1"); m["two"].push_back("2"); m["two"].push_back("3"); map_t::const_iterator i = m.begin(); i++; return 0; // <= break point on this line // neither "m" nor "i" are displayed in correct way } ~~~~~~~~~~~ Now run it and see how it's not possible to get access to the contents of the map of lists in a sane way using the gdb-mi commands: gdb -i mi ./a.out break 18 // assumes return 0; is on line 18 -var-create - * m // now compare this, esp. note the 'value="{...}"' -var-list-children --all-values var1 // with this print m // similarily compare the output of this: -var-create - * i // with the output of print i -- 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.
next reply other threads:[~2011-11-20 22:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-20 22:42 mail at milianw dot de [this message] 2011-11-21 11:46 ` [Bug mi/13419] " valentyn.pavliuchenko at gmail dot com 2012-08-22 17:29 ` tromey at redhat dot com 2014-09-12 23:05 ` sergiodj 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-13419-4717@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: linkBe 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).