public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Dieter Ferdinand" <dieter.ferdinand@gmx.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/8822: internal error segmentation fault Date: Fri, 21 Mar 2003 19:46:00 -0000 [thread overview] Message-ID: <20030321194601.31783.qmail@sources.redhat.com> (raw) The following reply was made to PR other/8822; it has been noted by GNATS. From: "Dieter Ferdinand" <dieter.ferdinand@gmx.de> To: bangerth@dealii.org, dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.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.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Von: bangerth@dealii.org Antwort an: bangerth@dealii.org, dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.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, ...
next reply other threads:[~2003-03-21 19:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-21 19:46 Dieter Ferdinand [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-15 18:49 bangerth 2003-01-11 17:06 Labbé Stéphane 2002-12-17 22:26 Dieter Ferdinand 2002-12-05 9:17 ehrhardt 2002-12-05 7:06 dieter.ferdinand
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=20030321194601.31783.qmail@sources.redhat.com \ --to=dieter.ferdinand@gmx.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).