Re: c++/1869: All C++ program segfault

Re: c++/1869: All C++ program segfault

[Phil Edwards]

The following reply was made to PR c++/1869; it has been noted by GNATS.

From: Phil Edwards <pedwards@disaster.jaj.com>
To: lukeskyfly@hotmail.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/1869: All C++ program segfault
Date: Mon, 5 Feb 2001 10:54:58 -0500

 On Sun, Feb 04, 2001 at 07:35:46PM -0000, lukeskyfly@hotmail.com wrote:
 > 
 > >Number:         1869
 > >Category:       c++
 > >Synopsis:       All C++ program segfault
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       high
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sun Feb 04 11:36:01 PST 2001
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Luke Mauldin
 > >Release:        CVS snapshot from 2-04-2001
 > >Organization:
 > >Environment:
 > RedHat 7.0, glibc 2.2.1, snapshot of binutils 2-04-2001.
 > >Description:
 > However, all shared libstdc++ tests fail with a build
 > time error
 
 The file testsuite/YYYYMMDD-mkchecklog.txt in the libstdc++ build directory
 will contain the error messages, if they are build errrors.
 
 
 > and when I try to run any c++ programs I complie with the new
 > snapshot, the programs segfault and do not leave any core file.
 
 The lack of a core file means that your system administrator has disabled
 core files.  Depending on local policy, you may be able to re-enable them
 briefly with either the "limit" or "ulimit" command (it varies based on
 what shell you use).  Ask your sysadmin for help in turning core files on.
 I would be interested in knowing what's failing where (you may have the
 same problem as I do).
 
 Phil
 
>From pbienst@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: pbienst@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/1679
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010307172602.26315.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg02082.html
Content-length: 622

The following reply was made to PR c++/1679; it has been noted by GNATS.

From: pbienst@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, zac@uni-oldenburg.de
Cc:  
Subject: Re: c++/1679
Date: 7 Mar 2001 17:16:59 -0000

 Synopsis: c++ -v -save-temps -DHAVE_CONFIG_H -I. -I. -I. -I./.. -isystem /usr/local/X11/include -DNDEBUG -O2 -g -W -Wall -trigraphs  -c HelpCB.C
 
 State-Changed-From-To: open->feedback
 State-Changed-By: pbienst
 State-Changed-When: Wed Mar  7 09:16:59 2001
 State-Changed-Why:
     Please provide preprocessed source
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1679&database=gcc

c++/1869: All C++ program segfault

[lukeskyfly]

>Number:         1869
>Category:       c++
>Synopsis:       All C++ program segfault
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 04 11:36:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Luke Mauldin
>Release:        CVS snapshot from 2-04-2001
>Organization:
>Environment:
RedHat 7.0, glibc 2.2.1, snapshot of binutils 2-04-2001.
>Description:
Can complie c programs and c programs work fine, even the Linux kernel(2.4.1).  However, all shared libstdc++ tests fail with a build time error and when I try to run any c++ programs I complie with the new snapshot, the programs segfault and do not leave any core file.  I have tried multiple c++ programs(simple and complex) and get the same result.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
>From bkoz@nabi.net Sun Apr 01 00:00:00 2001
From: benjamin kosnik <bkoz@nabi.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/2254
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010312184604.26118.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg02265.html
Content-length: 1490

The following reply was made to PR c++/2254; it has been noted by GNATS.

From: benjamin kosnik <bkoz@nabi.net>
To: gcc-gnats@gcc.gnu.org, steven@la-france.net, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/2254
Date: Mon, 12 Mar 2001 10:43:24 -0800

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2254&database=gcc
 
 
 This bug report is near-useless. Here's how you can make it better:
 
 1) just enclose the relevant bits of the make output:
 g++  -c -I/usr/X11R6/include -I/usr/local/qt/include
 -I/usr/X11R6/include -pipe -g -fPIC -DQT_BUILTIN_GIF_READER=1
 -DQT_NO_IMAGEIO_JPEG -DQT_NO_IMAGEIO_MNG 
 -I/usr/local/qt/src/3rdparty/zlib -I/usr/local/qt/src/3rdparty/libpng
 -I/usr/X11R6/include  -o dialogs/qfiledialog.o dialogs/qfiledialog.cpp
 In file included from dialogs/qfiledialog.cpp:49:
 /usr/local/qt/include/qlayout.h:156: Internal compiler error.
 /usr/local/qt/include/qlayout.h:156: Please submit a full bug report.
 /usr/local/qt/include/qlayout.h:156: See
 <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
 cpp: output pipe has been closed
 make[2]: *** [dialogs/qfiledialog.o] Error 1
 make[2]: Leaving directory `/usr/local/qt/src'
 make[1]: *** [sub-src] Error 2
 make[1]: Leaving directory `/usr/local/qt'
 make: *** [init] Error 2
 
 2) include pre-processed bits from the file the failed to compile.
 ie 'g++ -E dialogs/qfiledialog.cpp'
 
 3) narrow down the code to find the smallest possible example causing
 the crash.
 
 thanks,
 benjamin