Mailinglist Archive: opensuse-kde (130 mails)
| < Previous | Next > |
Re: [suse-kde] PROBLEM - gcc 3.2x segfault with 8.1/AthlonXP/VIAKT266A
- From: Matt Gibson <gothick@xxxxxxxxxxxxxx>
- Date: Wed, 18 Dec 2002 01:03:39 +0000
- Message-id: <200212180103.39840.gothick@xxxxxxxxxxxxxx>
On Tuesday 17 December 2002 21:51, PL O'Smith wrote:
> I think you meant for this to go back to the list, so I thought I would
> pass it along with some additions. I think Andrei has changed out the
Oops! Absolutely right, of course.
> changing with memtest? The fact that WinXP runs ok on the machine is
> not much of a test of the hardware or indication that the hardware is
> ok as Andrei seems to think.
I agree. The machine I had with the dodgy motherboard was running NT 4.0 dual
boot with Linux, and only compiling the kernel under Linux showed up the
problem. I saw maybe two bluescreens under NT for the couple of months I had
that motherboard, which was no more than average for NT4 *grin*.
The person who changed the motherboard in the end was a friend of mine who was
in the PC retail business at the time; he used to use gcc as a stress test
for new machines.
> If the install is an upgrade over a previous version of SuSE I am
> suspecting that there might be several gcc 2.95 programs still hanging
> around. If the install is new though, then my thoughts run to bad
> hardware or bad install/updates since then. If with a fresh install
> you have no problems, but after your updates you do, it's pretty likely
> something has gotten out of sync.
Yah. As I said before, I'm definitely thinking hardware myself, simply
because these are random crashes -- if gcc is broken in terms of
installation, I'd think it would normally die at the same place every time.
Cheers,
Matt
--
"It's the small gaps between the rain that count,
and learning how to live amongst them."
-- Jeff Noon
> I think you meant for this to go back to the list, so I thought I would
> pass it along with some additions. I think Andrei has changed out the
Oops! Absolutely right, of course.
> changing with memtest? The fact that WinXP runs ok on the machine is
> not much of a test of the hardware or indication that the hardware is
> ok as Andrei seems to think.
I agree. The machine I had with the dodgy motherboard was running NT 4.0 dual
boot with Linux, and only compiling the kernel under Linux showed up the
problem. I saw maybe two bluescreens under NT for the couple of months I had
that motherboard, which was no more than average for NT4 *grin*.
The person who changed the motherboard in the end was a friend of mine who was
in the PC retail business at the time; he used to use gcc as a stress test
for new machines.
> If the install is an upgrade over a previous version of SuSE I am
> suspecting that there might be several gcc 2.95 programs still hanging
> around. If the install is new though, then my thoughts run to bad
> hardware or bad install/updates since then. If with a fresh install
> you have no problems, but after your updates you do, it's pretty likely
> something has gotten out of sync.
Yah. As I said before, I'm definitely thinking hardware myself, simply
because these are random crashes -- if gcc is broken in terms of
installation, I'd think it would normally die at the same place every time.
Cheers,
Matt
--
"It's the small gaps between the rain that count,
and learning how to live amongst them."
-- Jeff Noon
| < Previous | Next > |