Date:	Tue, 15 Jun 1999 09:59:41 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Erik Berglund <erik2 DOT berglund AT telia DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: [erik2 DOT berglund AT telia DOT com: gcc-crash - and a possible solution]
In-Reply-To:	<199906142158.RAA22306@envy.delorie.com>
Message-ID:	<Pine.SUN.3.91.990615095842.2646L-100000@is>
MIME-Version:	1.0
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

> It seems to me that win3.11, and possibly win95, have a bug or "feature" in
> their DPMI providers, which sometimes could make gcc crash. Setting
> the crt0-bit would hopefully work around this bug.

FWIW, I don't remember any such reports for Windows 9X, and it has
*never* happened to me on Windows 95.

I think we need to investigate further, at least to know where does it
crash, exactly.

Is it possible for you to download binaries with debugging information
and post the traceback they generate?  Then somebody could look into
the code where it crashes and see what hints does that bring.

Andris, would it be enough that Erik downloads the latest binaries of
GCC 2.95 from SimTel and posts the traceback from them?  In other
words, do you have the same binary with debug info somewhere, so that
the traceback would be meaningful for you?

If not, perhaps you could arrange for unstripped binaries to be
available to Erik?

> Even though my system is now running nice and well, with the patch
> implemented, there could be
> potential problems for other djgpp-users, so I think the crt0-bit should be
> set in gcc, cpp etc,
> if you think that's a good idea.

This might be hiding the problem rather than solving it.  So before we
go out and change the startup flags, I think we need to understand the
problem some more.

Please note that this bit is not set by default for some very good
reasons: the Unixy sbrk algorithm breaks in some cases.

> One further argument would be that setting this crt0-bit is recommended for
> NT (according to FAQ section 3.3), and then I think it should be set
> also for win3.11 and win95, so we can use the same gcc-version on all OS's.

You forget about DOS, where that bit causes the most trouble.  Again,
no such problems were reported until now for other OSes (and when I
worked on Windows 3.X, I never had any crashes).

Do you, by any chance, have Win32s installed on your system?  Also, do
you have 32-bit file access enabled?  If the answer to both these
questions is YES, please try disabling one of these features and see
if that makes the crashes go away.

- Raw text -