public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/61262] GCC segfaults
2014-05-21 2:17 [Bug c++/61262] New: GCC segfaults lailavrazda1979 at gmail dot com
@ 2014-05-21 2:17 ` pinskia at gcc dot gnu.org
2014-05-21 2:56 ` lailavrazda1979 at gmail dot com
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2014-05-21 2:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal
^ permalink raw reply [flat|nested] 6+ messages in thread
* [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
* [Bug c++/61262] GCC segfaults
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
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: lailavrazda1979 at gmail dot com @ 2014-05-21 2:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262
--- Comment #1 from lailavrazda1979 at gmail dot com ---
A bug that causes GCC to segfault AND is a regression is only normal in
severity? I thought a crash is one of those things that should never, EVER
happen?
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/61262] GCC segfaults
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
4 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu.org @ 2014-05-21 7:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Please follow http://gcc.gnu.org/bugs.html , in particular please attach
preprocessed source that causes the ICE. What severity the bug will have is up
to the maintainers to decide when the bug is analyzed.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/61262] GCC segfaults
2014-05-21 2:17 [Bug c++/61262] New: GCC segfaults lailavrazda1979 at gmail dot com
` (2 preceding siblings ...)
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
4 siblings, 0 replies; 6+ messages in thread
From: rguenth at gcc dot gnu.org @ 2014-05-21 11:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2014-05-21
Ever confirmed|0 |1
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/61262] GCC segfaults
2014-05-21 2:17 [Bug c++/61262] New: GCC segfaults lailavrazda1979 at gmail dot com
` (3 preceding siblings ...)
2014-05-21 11:56 ` rguenth at gcc dot gnu.org
@ 2014-09-18 9:47 ` paolo.carlini at oracle dot com
4 siblings, 0 replies; 6+ messages in thread
From: paolo.carlini at oracle dot com @ 2014-09-18 9:47 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Feedback not forthcoming.
^ 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).