public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lailavrazda1979 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61262] New: GCC segfaults Date: Wed, 21 May 2014 02:17:00 -0000 [thread overview] Message-ID: <bug-61262-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262 Bug ID: 61262 Summary: GCC segfaults Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lailavrazda1979 at gmail dot com Since I code, I know that this is gonna be a pretty bad bug report. But I know next to nothing about the code I'm compiling, however, what I do know is, GCC 4.8.x works, while GCC 4.9.0 segfaults. Since I don't know the code, I'll provide complete steps to reproduce it: Clone https://github.com/monero-project/bitmonero.git Enter the new directory (bitmonero) Run: "make build-debug VERBOSE=1" Using the debug target is important; there seems to be other issue with building when the release target is used, and that will cause the build to terminate before the segfault. I get the following when building it with one thread: http://pastebin.com/EA3ydhHJ
next reply other threads:[~2014-05-21 2:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-21 2:17 lailavrazda1979 at gmail dot com [this message] 2014-05-21 2:17 ` [Bug c++/61262] " pinskia at gcc dot gnu.org 2014-05-21 2:56 ` lailavrazda1979 at gmail dot com 2014-05-21 7:50 ` jakub at gcc dot gnu.org 2014-05-21 11:56 ` rguenth at gcc dot gnu.org 2014-09-18 9:47 ` paolo.carlini at oracle 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-61262-4@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).