This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/1869: All C++ program segfault
- To: nobody at gcc dot gnu dot org
- Subject: Re: c++/1869: All C++ program segfault
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: 5 Feb 2001 15:46:00 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Phil Edwards <pedwards at disaster dot jaj dot com>
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