This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/61262] New: GCC segfaults
- From: "lailavrazda1979 at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 21 May 2014 02:17:01 +0000
- Subject: [Bug c++/61262] New: GCC segfaults
- Auto-submitted: auto-generated
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