* [Bug bootstrap/10227] Random segfaults
[not found] <20030326181601.10227.arbonline@users.sourceforge.net>
@ 2003-06-02 0:59 ` dhazeghi@yahoo.com
2003-06-02 13:27 ` arbonline@users.sourceforge.net
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: dhazeghi@yahoo.com @ 2003-06-02 0:59 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10227
------- Additional Comments From dhazeghi@yahoo.com 2003-06-02 00:59 -------
Hello,
would it be possible for you to check whether this problem occurs with gcc 3.3? Also, please note
that there were a number of bugs with -march=k6-2 earlier on, and if you compiled stuff with
those flags, they may well have ended up broken (for instance gcc 3.2.1), and the brokeness
exhibits itself in the form of a miscompiled, randomly segfaulting gcc 3.2.2. Thanks,
Dara
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug bootstrap/10227] Random segfaults
[not found] <20030326181601.10227.arbonline@users.sourceforge.net>
2003-06-02 0:59 ` [Bug bootstrap/10227] Random segfaults dhazeghi@yahoo.com
@ 2003-06-02 13:27 ` arbonline@users.sourceforge.net
2003-06-02 17:58 ` dhazeghi@yahoo.com
2003-06-02 18:50 ` pinskia@physics.uc.edu
3 siblings, 0 replies; 4+ messages in thread
From: arbonline@users.sourceforge.net @ 2003-06-02 13:27 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10227
------- Additional Comments From arbonline@users.sourceforge.net 2003-06-02 13:27 -------
Subject: Re: Random segfaults
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10227
I succefully build gcc-3.2.2 on the same machine with redhat gcc-3.2.2 so
I think I had some bug in the tool chain. It might be the bug on
march=k6-2.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug bootstrap/10227] Random segfaults
[not found] <20030326181601.10227.arbonline@users.sourceforge.net>
2003-06-02 0:59 ` [Bug bootstrap/10227] Random segfaults dhazeghi@yahoo.com
2003-06-02 13:27 ` arbonline@users.sourceforge.net
@ 2003-06-02 17:58 ` dhazeghi@yahoo.com
2003-06-02 18:50 ` pinskia@physics.uc.edu
3 siblings, 0 replies; 4+ messages in thread
From: dhazeghi@yahoo.com @ 2003-06-02 17:58 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10227
dhazeghi@yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC build triplet| |i686-pc-linux-gnu
GCC host triplet| |i686-pc-linux-gnu
GCC target triplet| |i686-pc-linux-gnu
------- Additional Comments From dhazeghi@yahoo.com 2003-06-02 17:58 -------
Hello,
so then is this bug still present? Are you going to be able to check with gcc 3.3? Thanks,
Dara
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug bootstrap/10227] Random segfaults
[not found] <20030326181601.10227.arbonline@users.sourceforge.net>
` (2 preceding siblings ...)
2003-06-02 17:58 ` dhazeghi@yahoo.com
@ 2003-06-02 18:50 ` pinskia@physics.uc.edu
3 siblings, 0 replies; 4+ messages in thread
From: pinskia@physics.uc.edu @ 2003-06-02 18:50 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10227
pinskia@physics.uc.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
------- Additional Comments From pinskia@physics.uc.edu 2003-06-02 18:50 -------
It really looks like it was a hardware problem because they were getting an seg faults at
different places, so closing as Invalid. Try a memory checker to find out where your
problem is.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 4+ messages in thread