public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/31502] gcc/g++ randomly seg faults, sometimes freezes the entire machine
Date: Sat, 07 Apr 2007 15:29:00 -0000	[thread overview]
Message-ID: <20070407152938.24514.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31502-14370@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from bangerth at dealii dot org  2007-04-07 16:29 -------
(In reply to comment #2)
> I'm willing to accept this as an hardware/OS issue, but then am I really that
> unlikely to be the only person having this kind of problem? In other words, has
> this type of problems been seen before and if so, how were they resolved?

There's an easy way to figure out whether it's the compiler's fault or that
of your machine: does the error always happen on the same file, with the
exact same error message? Since gcc is a deterministic program, it would have
to cause the same problem every time you compile the same file.

On the other hand, if the error appears randomly even though you compile
the same set of files, then this clearly can't be gcc's fault.

It certainly sounds like a hardware problem (memory, overheating, disk, ...)
W.


-- 

bangerth at dealii dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bangerth at dealii dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31502


  parent reply	other threads:[~2007-04-07 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-07 11:45 [Bug c++/31502] New: " ye dot patrick at gmail dot com
2007-04-07 14:31 ` [Bug c++/31502] " pinskia at gcc dot gnu dot org
2007-04-07 14:43 ` ye dot patrick at gmail dot com
2007-04-07 15:29 ` bangerth at dealii dot org [this message]
2007-04-08  3:39 ` ye dot patrick at gmail dot com
2007-05-07  1:54 ` bgoodr+gccbugzilla at gmail dot com
2007-05-07  2:00 ` pinskia at gcc dot gnu dot org
2007-05-07  3:19 ` bgoodr+gccbugzilla at gmail 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=20070407152938.24514.qmail@sourceware.org \
    --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: link
Be 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).