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++/53455] boost::python segfault Date: Thu, 14 Jun 2012 13:15:00 -0000 [thread overview] Message-ID: <bug-53455-4-OeqU8pGtoA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53455-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53455 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE --- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-06-14 13:15:30 UTC --- I think this is a duplicate of PR 53657, the crash happens returning a std::pair and goes away if the move ctor is trivial *** This bug has been marked as a duplicate of bug 53657 ***
next prev parent reply other threads:[~2012-06-14 13:15 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-22 17:41 [Bug c++/53455] New: g++ builds segfault in boost::python j.wielicki at sotecware dot net 2012-05-22 17:42 ` [Bug c++/53455] " j.wielicki at sotecware dot net 2012-05-22 17:50 ` j.wielicki at sotecware dot net 2012-05-22 18:36 ` s_gccbugzilla at nedprod dot com 2012-05-22 19:08 ` rene.kuettner at gmail dot com 2012-05-22 20:08 ` [Bug c++/53455] boost::python segfault s_gccbugzilla at nedprod dot com 2012-05-24 14:29 ` ndbecker2 at gmail dot com 2012-05-24 14:42 ` org.gnu.gcc.bugtracker at sotecware dot net 2012-05-24 15:10 ` org.gnu.gcc.bugtracker at sotecware dot net 2012-06-13 22:14 ` mbec at gmto dot org 2012-06-14 0:47 ` mbec at gmto dot org 2012-06-14 11:49 ` s_gccbugzilla at nedprod dot com 2012-06-14 12:51 ` redi at gcc dot gnu.org 2012-06-14 13:15 ` redi at gcc dot gnu.org [this message] 2012-06-14 13:22 ` redi at gcc dot gnu.org 2012-06-14 13:25 ` s_gccbugzilla at nedprod dot com 2012-06-14 13:27 ` org.gnu.gcc.bugtracker at sotecware dot net 2012-06-14 14:01 ` redi at gcc dot gnu.org 2012-06-14 15:15 ` s_gccbugzilla at nedprod dot com 2012-06-14 15:21 ` org.gnu.gcc.bugtracker at sotecware dot net 2012-06-14 15:45 ` redi at gcc dot gnu.org 2012-06-14 16:10 ` org.gnu.gcc.bugtracker at sotecware dot net 2012-06-14 16:16 ` s_gccbugzilla at nedprod dot com 2012-06-14 16:22 ` redi at gcc dot gnu.org 2012-06-14 16:24 ` redi at gcc dot gnu.org 2012-06-14 16:37 ` s_gccbugzilla at nedprod dot com
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-53455-4-OeqU8pGtoA@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).