Re: 20040214 no fix for unzip, cygwin debugging howto?

2004-02-16 Thread Christopher Faylor
On Mon, Feb 16, 2004 at 12:09:44AM -0500, Thomas L Roche wrote: >Thomas L Roche Mon, 16 Feb 2004 00:01:10 -0500 >> Unfortunately 20040215 came out while I was debugging 20042014. >> Since you > >do not > >> claim to have done anything that might have actually fixed the >> problem, the results obtai

RE: 20040214 no fix for unzip, cygwin debugging howto?

2004-02-16 Thread Ken Thompson
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Thomas L Roche > Sent: Monday, February 16, 2004 12:01 AM > To: [EMAIL PROTECTED] > Subject: Re: 20040214 no fix for unzip, cygwin debugging howto? > > > Christopher Faylo

Re: 20040214 no fix for unzip, cygwin debugging howto?

2004-02-15 Thread Thomas L Roche
Thomas L Roche Mon, 16 Feb 2004 00:01:10 -0500 > Unfortunately 20040215 came out while I was debugging 20042014. > Since you do not > claim to have done anything that might have actually fixed the > problem, the results obtained at > http://cygwin.com/ml/cygwin/2004-02/msg00705.html > are still

Re: 20040214 no fix for unzip, cygwin debugging howto?

2004-02-15 Thread Thomas L Roche
Christopher Faylor Sun, 15 Feb 2004 21:12:02 -0500 > it occurred to me that I could add some increased debugging which > might show why cmalloc was returning NULL. How thoughtful of you. > So, the next snapshot will have more strace output for the failing > condition, meaning that if you do this: