public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53490] Segmentation Fault when accessing std::set Date: Sat, 26 May 2012 00:14:00 -0000 [thread overview] Message-ID: <bug-53490-4-E5m2ONjdlc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53490-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53490 --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-26 00:02:13 UTC --- (In reply to comment #4) > It was a vanilla bjam build of boost 1.49, so > no -std=c++11. Then technically that's not supported, since there are no guarantees of link-compatibility between -std=c++98 and -std=c++11 code (but I'm not aware of any specific reasons it wouldn't work for a std::set) (In reply to comment #5) > For clarity I should say I just tried with a vanilla build of 1.47 and get > essentially the same backtrace here. I don't think the build of boost 1.47 I used earlier was non-vanilla in any way, and I get no segfault on Fedora 16 using the system's boost-static-1.47.0-6.fc16.x86_64.rpm with: ~/gcc/4.7/bin/g++ j.cc -std=c++11 -Wl,-Bstatic -lboost_program_options -Wl,-Bdynamic Is it significant that you link statically? Does it fail in the same way if you link dynamically?
next prev parent reply other threads:[~2012-05-26 0:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-25 18:13 [Bug c++/53490] New: " ja11sop at yahoo dot co.uk 2012-05-25 18:22 ` [Bug c++/53490] " redi at gcc dot gnu.org 2012-05-25 18:24 ` redi at gcc dot gnu.org 2012-05-25 20:42 ` daniel.kruegler at googlemail dot com 2012-05-25 22:16 ` ja11sop at yahoo dot co.uk 2012-05-25 22:51 ` ja11sop at yahoo dot co.uk 2012-05-26 0:14 ` redi at gcc dot gnu.org [this message] 2012-05-26 13:26 ` ja11sop at yahoo dot co.uk 2012-05-28 9:32 ` ja11sop at yahoo dot co.uk 2012-05-28 9:40 ` 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-53490-4-E5m2ONjdlc@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: 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).