From: bughuntr AT one DOT ctelcom DOT net (Bug Hunter)
Subject: RE: B19 crash, tetris compile fixed
3 Mar 1998 18:10:06 -0800
Message-ID: <Pine.LNX.3.95.980303083239.28262G-100000.cygnus.gnu-win32@one.ctelcom.net>
References: <01BD4691 DOT 33EF6090 AT gater DOT krystalbank DOT msk DOT ru>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: Sergey Okhapkin <sos AT prospect DOT com DOT ru>
Cc: gnuwin32 <gnu-win32 AT cygnus DOT com>


  Interesting.  After only 3 times, I get it to crash.  It is wholly
reproducable.  I've noticed random freezes commented on from others. It
may be due to no service packs applied to windows 95 on my part.  I will
try applying them and find out.

  Is this with or without your fdopen() fix?  That may be the root cause
of the crash.

  Yes, you tried enough.  Have you tried to pipe to a non-existant
program?

bug

On Tue, 3 Mar 1998, Sergey Okhapkin wrote:

> Bug Hunter wrote:
> >   I understand.  My message's intent was to provide a method to recreate
> > the crash. Setenv was just what I tried the first time until I figured it
> > was not available. I've found that bash 2.01.1 will crash for any "command
> > not found" if repeated multiple times, and it will crash for any pipe to a
> 
> I can't reproduce a bug, is this enough:
> 
> 1:~$ setenv
> bash.exe: setenv: command not found
> 2:~$ setenv
> bash.exe: setenv: command not found
> 3:~$ setenv
> bash.exe: setenv: command not found
> 4:~$ setenv
<cut>

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".