public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ja11sop at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53490] Segmentation Fault when accessing std::set
Date: Mon, 28 May 2012 09:32:00 -0000 [thread overview]
Message-ID: <bug-53490-4-QGKg36iJMs@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 #8 from Jamie Allsop <ja11sop at yahoo dot co.uk> 2012-05-28 09:09:30 UTC ---
(In reply to comment #7)
> (In reply to comment #6)
> > (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)
> >
>
> So after sifting through the jam files to confirm there is no -std=c++11 set in
> boost for gcc4.7 I modified my bjam invocations to add cxxflags="-std=c++11"
> and now the test runs without the segfault. Verifying now on the full code
> base. When the tests cycle and presumably pass I'll post back. It does look
> however as if the mismatch in compile flags is the culprit here. Apologies for
> not being thorough in checking that earlier.
All tests cycled and passed so I'd say this issue is understood now and user
error.
next prev parent reply other threads:[~2012-05-28 9:09 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
2012-05-26 13:26 ` ja11sop at yahoo dot co.uk
2012-05-28 9:32 ` ja11sop at yahoo dot co.uk [this message]
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-QGKg36iJMs@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).