public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tcallawa at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/53218] cmake segfaults on sparcv9
Date: Thu, 03 May 2012 19:47:00 -0000 [thread overview]
Message-ID: <bug-53218-4-LxJ5JxgLiF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53218-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53218
--- Comment #1 from Tom Callaway <tcallawa at redhat dot com> 2012-05-03 19:47:15 UTC ---
Also seeing a very similar segfault with source-highlight (same environment,
Linux/sparcv9/32bit userspace):
(gdb) bt
#0 0xf7ae0d98 in __frame_dummy_init_array_entry () from /lib/libstdc++.so.6
#1 0xf7a46f08 in __cxxabiv1::__cxa_get_globals () at
../../../../libstdc++-v3/libsupc++/eh_globals.cc:63
#2 0xf7a46d4c in std::uncaught_exception () at
../../../../libstdc++-v3/libsupc++/eh_catch.cc:136
#3 0xf7a82c44 in ~sentry (this=0xff9781e0, __in_chrg=<optimized out>) at
/usr/src/debug/gcc-4.7.0-20120502/obj-sparc64-redhat-linux/sparc64-redhat-linux/libstdc++-v3/include/ostream:429
#4 std::__ostream_insert<char, std::char_traits<char> > (__out=...,
__s=<optimized out>, __n=<optimized out>)
at
/usr/src/debug/gcc-4.7.0-20120502/obj-sparc64-redhat-linux/sparc64-redhat-linux/libstdc++-v3/include/bits/ostream_insert.h:112
#5 0x00013a6c in main (argc=<optimized out>, argv=<optimized out>) at
source-highlight.cc:435
next prev parent reply other threads:[~2012-05-03 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 19:42 [Bug libstdc++/53218] New: " tcallawa at redhat dot com
2012-05-03 19:47 ` tcallawa at redhat dot com [this message]
2012-05-05 19:46 ` [Bug libstdc++/53218] " ebotcazou at gcc dot gnu.org
2012-05-07 13:34 ` tcallawa at redhat dot com
2012-05-07 13:38 ` ebotcazou at gcc dot gnu.org
2012-05-29 14:34 ` [Bug libstdc++/53218] [4.7 regression] " rguenth at gcc dot gnu.org
2012-06-14 8:12 ` rguenth at gcc dot gnu.org
2012-09-20 10:14 ` jakub at gcc dot gnu.org
2012-12-03 15:27 ` rguenth at gcc dot gnu.org
2013-01-09 1:07 ` pinskia 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-53218-4-LxJ5JxgLiF@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).