From: Andrew Lees <andrewl_oz@bigpond.com>
To: Oliver Kullmann <O.Kullmann@Swansea.ac.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Internal compiler error: Segmentation fault
Date: Tue, 29 Jul 2003 12:43:00 -0000 [thread overview]
Message-ID: <200307291700.51832.andrewl_oz@bigpond.com> (raw)
In-Reply-To: <20030722210141.GA25238@swan.ac.uk>
On Wednesday 23 July 2003 07:01, Oliver Kullmann wrote:
> Hi,
>
> I just wanted to finish a quick job, but with my
> g++ version 3.3 (prelease, Suse 8.2) I got
> a compiler segmentation fault. So I downloaded
>
On the occasions I have encountered a segfault using gcc, it has invariably
been due to a hardware fault with my system. Gcc has been the best hardware
diagnostic tool I have encountered, but I have no idea why it should be so
sensitive in this way. Others have had a similar experience. Whilst it may
not always be the case, it could be a good idea to run a comprehensive memory
test, etc on your machine on the offchance you are having a similar
experience.
Regards,
Andy Lees.
next prev parent reply other threads:[~2003-07-29 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 21:46 Oliver Kullmann
2003-07-23 14:46 ` LLeweLLyn Reese
2003-07-23 16:06 ` Oliver Kullmann
2003-07-29 12:43 ` Andrew Lees [this message]
2005-07-20 15:32 internal " J. David Boyd
2007-06-30 12:28 Lee Rhodes
2023-04-08 15:15 Dennis Clarke
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=200307291700.51832.andrewl_oz@bigpond.com \
--to=andrewl_oz@bigpond.com \
--cc=O.Kullmann@Swansea.ac.uk \
--cc=gcc-help@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).