From:	pavenis AT lanet DOT lv
Message-ID:	<B0000090800@stargate.astr.lu.lv>
To:	"Erik Berglund" <erik2 DOT berglund AT telia DOT com>, djgpp-workers AT delorie DOT com
Date:	Wed, 16 Jun 1999 20:25:32 +0300
MIME-Version:	1.0
Subject:	Re: Re: gcc-crash - and a possible solution
In-reply-to:	<MAPI.Id.0016.00333138303633303030303930303039@MAPI.to.RFC822>
X-mailer:	Pegasus Mail for Win32 (v3.11)
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 16 Jun 99, at 18:25, Erik Berglund wrote:

> 
> Eli Zaretskii wrote:
> 
> > I think we need to investigate further, at least to know where does it
> > crash, exactly.
> 
> I agree on that. Would it be possible for you to rebuild GCC 2.7.2.1 with 
> DJGPP 2.01 on your site and use my register dump (posted on 14 Jun 1999)
> to tell where the code fails?

I'm afraid it would be rather difficult to get identical binaries.  
Therefore I think we should in future either leave binaries not 
stripped or put not stripped binaries somewhere.

> Otherwise, I can install for instance GCC 2.8.1 with DJGPP 2.02 and try to 
> reproduce the error.

I built last binaries of gcc-2.8.1 using beta version of DJGPP-2.02. 
Therefore also it will be difficult to reproduce them exactly.

However there is one possibility. I'm going to make available 
DJGPP binaries of todays snapshot of gcc-2.95 prerelesea 
(egcs-19990616) which appears to be rather stable (I used slightly 
patched previous snapshot for my own programs and also compiling
prerelease itself, built rhtvision-1.06 and it works, etc.). There were 
one problem (#pragma pack() were broken but this is now fixed)

So I suggest to try this version. I'll make at least C and C++ 
compiler binaries available at 
	http://www.lanet.lv/~pavenis/djgpp.html

Currently there are stripped binaries of 8 June snapshot, but after 
short testing I'll put the 16th June snapshot binaries there (without 
stripping them)

Andris

- Raw text -