This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: other/8822: internal error segmentation fault
- From: "Dieter Ferdinand" <dieter dot ferdinand at gmx dot de>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 21 Mar 2003 19:46:01 -0000
- Subject: Re: other/8822: internal error segmentation fault
- Reply-to: "Dieter Ferdinand" <dieter dot ferdinand at gmx dot de>
The following reply was made to PR other/8822; it has been noted by GNATS.
From: "Dieter Ferdinand" <dieter dot ferdinand at gmx dot de>
To: bangerth at dealii dot org, dieter dot ferdinand at gmx dot de,
gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org,
gcc-gnats at gcc dot gnu dot org
Cc:
Subject: Re: other/8822: internal error segmentation fault
Date: Fri, 21 Mar 2003 20:39:44 +1
hello,
i have used a dual-processor-system with 2 p-200 to compile gcc 3.1.
when i boot without smp-support, this works fine, when i boot with smp support, the
compiler crash with an internal error.
i test it under some different linux-versions (2.2 and 2.4) and have the same error.
i can't say more to this error, i can only give you access to this system, to test it self.
i can also test it on some other dual-systems, but this doen't solve the problem.
how can i dealtivate the theading functions for gcc ?
goodby
Datum: 15 Mar 2003 18:49:42 -0000
An: dieter dot ferdinand at gmx dot de, gcc-bugs at gcc dot gnu dot org,
gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
Von: bangerth at dealii dot org
Antwort an: bangerth at dealii dot org, dieter dot ferdinand at gmx dot de,
gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org,
nobody at gcc dot gnu dot org,
gcc-gnats at gcc dot gnu dot org
Betreff: Re: other/8822: internal error segmentation fault
> Synopsis: internal error segmentation fault
>
> State-Changed-From-To: feedback->closed
> State-Changed-By: bangerth
> State-Changed-When: Sat Mar 15 18:49:42 2003
> State-Changed-Why:
> Whatever the cause may be, if we are to fix something then
> we need a _reproducible_ testcase.
>
> At any rate, repeated sporadic errors on a widely
> available system on which gcc is built daily are not
> enough to describe a bug.
>
> W.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8822
>
>
Schau auch einmal auf meine Homepage (http://go.to/dieter-ferdinand).
Dort findest du Information zu Linux, Novell, Win95, WinNT, ...