On Sun, Feb 15, 2004 at 01:06:32PM -0500, Christopher Faylor wrote: >On Sun, Feb 15, 2004 at 12:59:30PM -0500, Thomas L Roche wrote: >>Christopher Faylor Sun, 15 Feb 2004 12:16:59 -0500 ----- >>> No one is *trying* to fix unzip, >> >>But are they trying to fix *cygwin1.dll*, which seems to have strewn >>breakage in its wake? > >Feel free to check unzip after every dll update but I'm telling you that >no one is investigating your problem. Therefore, it is very unlikely >that it will be fixed and, so, it will be basically noise for you to >send email here reporting continued breakage. > >It is not useful to send a "it still doesn't work" message after new >snapshots when there is no activity directed towards fixing your >problem.
After sending this, it occurred to me that I could add some increased debugging which might show why cmalloc was returning NULL. So, the next snapshot will have more strace output for the failing condition, meaning that if you do this: strace -o strace.out unzip whatever it should produce a large strace file. The only interesting output for now would come from the _csbrk function which will have words like "couldn't commit memory for cygwin heap..." in it. If you are interested in tracking this down, please send the information from that line here. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
