Date: Wed, 10 Nov 1999 14:08:23 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Chris Ho-Stuart <hostuart AT sky DOT fit DOT qut DOT edu DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: Segmentation violation core dump blues
In-Reply-To: <808ct1$fj2$1@dove.qut.edu.au>
Message-ID: <Pine.SUN.3.91.991110140805.8611f-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 9 Nov 1999, Chris Ho-Stuart wrote:

> Recently I have been having trouble with djgpp compiled utilities
> getting a segmentation violation on my Windows NT console window.
> 
> Here, for example, is an attempt to run "ls".

Can you reproduce such crashes with any of the programs you yourself
compile?  If so, please run SYMIFY when it crashes and post here the
SYMIFY'ed traceback (more than one, if they differ).

> This version of ls came in the fil316b package of UNIX like utilities.

FWIW, the same binary of `ls' works for me on NT 4SP3.

(Just in case: is your ls.exe dated Apr 18, 1997?)

> gcc itself also fails sometimes in (I think) the linking stage, with
> similar messages.

Add -v to the GCC command line, and you will see *exactly* where it
crashes.

What version of GCC is that?