public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/61262] New: GCC segfaults
@ 2014-05-21  2:17 lailavrazda1979 at gmail dot com
  2014-05-21  2:17 ` [Bug c++/61262] " pinskia at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: lailavrazda1979 at gmail dot com @ 2014-05-21  2:17 UTC (permalink / raw)
  To: gcc-bugs

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-09-18  9:47 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-05-21  2:17 [Bug c++/61262] New: GCC segfaults lailavrazda1979 at gmail dot com
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

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).