public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/55041] prettyprinting/shared_ptr & cxx11 fails on some platforms
Date: Thu, 24 Jan 2013 18:52:00 -0000 [thread overview]
Message-ID: <bug-55041-4-Lz5PtZtil0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55041-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55041
--- Comment #16 from Tom Tromey <tromey at gcc dot gnu.org> 2013-01-24 18:50:58 UTC ---
(In reply to comment #12)
> In my case the issue seems to be weird debuginfo emitted by gcc;
> look at what the breakpoint reports:
>
> Breakpoint 1, _GLOBAL__sub_I__Z4makem () at
> /home/tromey/Space/Trunk/Git/gcc/lib
> stdc++-v3/testsuite/libstdc++-prettyprinters/shared_ptr.cc:81
FWIW this problem doesn't appear with a more recent trunk gcc.
I tried one from Jan 17 (c1f9696864b1b8ab20a6798751eec48986a2e98a)
just now.
Are there still unresolved problems in this bug?
next prev parent reply other threads:[~2013-01-24 18:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 18:59 [Bug libstdc++/55041] New: " bkoz at gcc dot gnu.org
2012-10-23 20:54 ` [Bug libstdc++/55041] " redi at gcc dot gnu.org
2012-10-23 21:11 ` paolo.carlini at oracle dot com
2012-10-24 10:43 ` paolo.carlini at oracle dot com
2012-10-24 11:21 ` redi at gcc dot gnu.org
2012-10-24 11:59 ` paolo.carlini at oracle dot com
2012-10-28 12:54 ` redi at gcc dot gnu.org
2012-10-28 13:21 ` redi at gcc dot gnu.org
2012-10-28 13:27 ` redi at gcc dot gnu.org
2012-10-28 13:37 ` redi at gcc dot gnu.org
2012-10-28 13:57 ` redi at gcc dot gnu.org
2012-11-16 18:14 ` redi at gcc dot gnu.org
2012-11-16 20:47 ` tromey at gcc dot gnu.org
2012-11-17 0:48 ` redi at gcc dot gnu.org
2012-11-17 13:27 ` mark at gcc dot gnu.org
2012-11-20 0:10 ` redi at gcc dot gnu.org
2013-01-24 18:52 ` tromey at gcc dot gnu.org [this message]
2013-01-24 18:55 ` bkoz 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-55041-4-Lz5PtZtil0@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).