Xref: utzoo gnu.g++.bug:1450 gnu.g++.lib.bug:289
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!orc!oli-stl!asylum!rpx!rp
From: rp@rpx.UUCP (Rich Patterson)
Newsgroups: gnu.g++.bug,gnu.g++.lib.bug
Subject: Re: Global string constant causes core dump g++/libg++ 1.36.x on 386
Summary: The problem was with ld versus ld++.
Keywords: G++ LIBG++ 386 System V
Message-ID: <545@rpx.UUCP>
Date: 11 Feb 90 09:12:33 GMT
References: <2019@osc.COM>
Followup-To: gnu.g++.bug
Lines: 20

In article <2019@osc.COM>, rp@osc.COM (Rich Patterson) writes:
> Hi,
> 	Here is a problem that I've found in g++/libg++. Flames --> /dev/null.
> 
> Synopsis: __CTOR_LIST__ is invalid for the following program (G++-1.36.4/
> 	  LIBG++-1.35.3 386 System V GAS and COFF encapsulaton) and dumps
> 	  core.  Initialized global string constant causes problems.
> 

I found the problem.  The problem was I was using ld instead of ld++.  I had
tried ld++ earlier and, ld++ itself core dumped on my while linking.  It had
something to do with cplus-dem.c.  When I built ld++ the first time it
needed 'index' (which is incompatible on SysV) instead of strchr.  I recompiled
it using strchr and both the linker and program work just fine now.

Rich P.
rp@osc	[by day]
{pacbell,amdcad}!osc!rp
rp@rpx	[by night]
{pyramid,zycad}!rpx!rp