Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Thu, 2 Mar 2000 16:52:12 -0500 From: Glenn Spell To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Still 100% usage and weird problems with recent snapshots? Message-ID: <20000302165211.A16660@shell4.ba.best.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com References: <38B89AEA DOT 2FFB9F85 AT ece DOT gatech DOT edu> <38BE0783 DOT 3D27966D AT ece DOT gatech DOT edu> <20000302131339 DOT B20207 AT cygnus DOT com> <20000302160009 DOT A3895 AT shell4 DOT ba DOT best DOT com> <20000302160607 DOT D21993 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000302160607.D21993@cygnus.com>; from "Chris Faylor" on Thu, Mar 02, 2000 at 04:06PM Organization: the aerie On 2 Mar 2000 around 4:06PM (-0500) Chris Faylor wrote: > On Thu, Mar 02, 2000 at 04:00:10PM -0500, Glenn Spell wrote: > > > >As I reported earlier, the bash I was using up until recently will > >not run with any snapshots after the 99-12-04. The only thing I am > >aware of about this bash-2.03 that won't run is that I compiled it > >with gcc-2.95 (I have not yet updated gcc from 2.95.) > > You reported that you were having problems but I don't recall anything > that indicated you still had problems with the newest snapshot. I figure that I'll need to upgrade gcc, rebuild bash, and then see if there is any problem... and I doubt if there will be or others would be seeing it also. I don't have plans at the moment to upgrade gcc. I haven't filed any other reports because this is not really a problem that I need solved. I'm reporting now just in case it can help you trace something that may be affecting others in different ways. > It is not conceivable that gdb would report that you are stopped at > the code that you show below and that no strace output shows up. It is for me. ;-) > How are you running the strace program? I move to the directory where I'm keeping the bash that doesn't work, a directory that is not in my path, and I strace ./bash and nothing happens. "^C" gets me out. > You should do something like this: > > strace -osomefile bash strace -otestout ./bash hangs... nothing happens. The file "testout" is created. I CTRL-C and end the process. Checking "testout" with pfe shows an empty file. Checking it with Hex Edit shows only "00000000 " (without the quotes) (This is using the strace and DLL from DJ's latest preview. -glenn -- ________________________________________ _ _____ ) )_ _ (__\____o /_/_ | ) Glenn Spell ) >-----._/_/__]> )________________________________________) `0 | -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com