From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14066 invoked by alias); 1 Apr 2003 07:06:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 14052 invoked by uid 71); 1 Apr 2003 07:06:01 -0000 Date: Tue, 01 Apr 2003 07:06:00 -0000 Message-ID: <20030401070601.14051.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Patrick Subject: Re: other/10279: g++ exits with segmentation-fault Reply-To: Patrick X-SW-Source: 2003-04/txt/msg00012.txt.bz2 List-Id: The following reply was made to PR other/10279; it has been noted by GNATS. From: Patrick To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, plax@chemie.uni-dortmund.de, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/10279: g++ exits with segmentation-fault Date: Tue, 1 Apr 2003 08:57:30 +0200 Hallo bangerth@dealii.org! I am very sure that this is not a hardware bug. In fact, I run this computer for three months now with Slackware 9.0-pre and now Slackware 9.0.0 without any problems. gcc3 is the only program that has these crashes, in Slackware 9.0-pre I installed gcc2 and it worked quite fine. I have used memtest86 over one weekend and it didn't report any errors with the ram. I am sorry for not telling you the flags for compilation, but I am more a "./configure && make"-user than a real programmer. To cite the output by make: g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../dcop -I../../libltdl -I../../kdecore \ -I../../kdeui -I../../kio -I../../kio/kio -I../../kio/kfile -I../.. -I/usr/lib/qt/include \ -I. -I/opt/kde/include -DQT_THREAD_SUPPORT -D_REENTRANT \ -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic -W \ -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi \ -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align \ -Wconversion -O2 -fno-exceptions -fno-check-new \ -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE \ -DQT_NO_ASCII_CAST -DQT_NO_COMPAT -c \ -o dcop.o `test -f 'dcop.cpp' || echo './'`dcop.cpp About the frequency of the segmentation faults: In a software package like kdelibs-3.1.1, I get about 20-30 of these segmentation faults, so on this system I am unable to use gcc3. Regarding this frequency and the experienced stability of other software on my system, I am sure that this is an error in gcc3 or any of its development tools/libs. If you are interested in following this bug and you need more information, please send an email to me. At the moment I have no idea which more information is useful for you because I'm not a programmer. Nevertheless I am rather willing to help you if I can, although I have now decided to downgrade back to gcc2. Sincerely, Patrick Du schriebst am Montag, 31. März 2003 18:10: > Synopsis: g++ exits with segmentation-fault > > State-Changed-From-To: open->closed > State-Changed-By: bangerth > State-Changed-When: Mon Mar 31 16:10:19 2003 > State-Changed-Why: > Compiles fine for me. Two remarks: > - you don't tell us which flags you used for compilation > - sporadic non-reproducible crashed are more often than not > problems with the hardware, in particular bad memory > sticks. Try running a memory checking tool for a night > on your machine to find out whether this is really the > problem. > > Wolfgang > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc& >pr=10279