public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asmwarrior at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/53477] pretty printer fails with: Python Exception <type 'exceptions.IndexError'> list index out of range
Date: Mon, 03 Jun 2013 04:05:00 -0000 [thread overview]
Message-ID: <bug-53477-4-I14t24qlFC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53477-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53477
--- Comment #5 from asmwarrior <asmwarrior at gmail dot com> ---
> p /r m_Headers
[debug]> p /r m_Headers
[debug]$5 = (StringSet &) @0x116d0bc4: {_M_t = {_M_impl =
{<std::allocator<std::_Rb_tree_node<wxString> >> =
{<__gnu_cxx::new_allocator<std::_Rb_tree_node<wxString> >> = {<No data
fields>}, <No data fields>}, _M_key_compare = {<std::binary_function<wxString,
wxString, bool>> = {<No data fields>}, <No data fields>}, _M_header = {_M_color
= std::_S_red, _M_parent = 0x116d2d28, _M_left = 0x116d2d28, _M_right =
0x116d2d28}, _M_node_count = 1}}}
[debug]>>>>>>cb_gdb:
When I see the E:\code\gcc\PCXMinGW463\bin\libstdcxx\v6\printers.py, I see in
the line: 476
def children (self):
rep_type = find_type(self.val.type, '_Rep_type')
node = find_type(rep_type, '_Link_type')
node = node.strip_typedefs()
return self._iter (RbtreeIterator (self.val), node)
The variable is declared as: StringSet& m_Headers;
and the StringSet is defined as: typedef std::set<wxString> StringSet;
Hope those information can help to solve this bug.
next prev parent reply other threads:[~2013-06-03 4:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 17:02 [Bug libstdc++/53477] New: " pluto at agmk dot net
2012-07-13 18:38 ` [Bug libstdc++/53477] " tromey at gcc dot gnu.org
2012-07-16 17:57 ` pinskia at gcc dot gnu.org
2012-07-16 19:03 ` pluto at agmk dot net
2013-06-03 3:41 ` asmwarrior at gmail dot com
2013-06-03 3:47 ` asmwarrior at gmail dot com
2013-06-03 4:05 ` asmwarrior at gmail dot com [this message]
2013-06-03 7:21 ` asmwarrior at gmail dot com
2013-06-03 7:34 ` asmwarrior at gmail dot com
2013-06-14 20:39 ` tomga at wp dot pl
2013-06-15 12:06 ` tomga at wp dot pl
2013-07-07 14:16 ` tomga at wp dot pl
2013-08-21 9:01 ` pmuldoon at redhat dot com
2013-08-21 9:42 ` redi at gcc dot gnu.org
2013-08-21 13:44 ` pmuldoon at redhat dot com
2013-08-21 13:46 ` mpolacek at gcc dot gnu.org
2013-08-22 19:14 ` pluto at agmk dot net
2014-01-06 11:36 ` pluto at agmk dot net
2014-05-06 8:36 ` jiyouguo at gmail dot com
2014-05-06 9:11 ` redi at gcc dot gnu.org
2014-05-07 12:55 ` jiyouguo at gmail dot com
2015-05-22 16:49 ` redi at gcc dot gnu.org
2015-05-22 20:12 ` tomga at wp dot pl
2015-05-23 9:57 ` redi at gcc dot gnu.org
2015-05-24 8:09 ` tomga at wp dot pl
2015-05-24 22:49 ` redi at gcc dot gnu.org
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-53477-4-I14t24qlFC@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).