unzip problem after upgrading

Thomas L Roche tlroche@us.ibm.com
Thu Feb 12 02:12:00 GMT 2004


On Tue, 3 Feb 2004, Thomas L Roche wrote:
>>> However I'm also, again only since upgrading [cygwin, from
>>> 1.5.5-1], having problems with unzip, e.g.

>>>> inflating:
>>> 
/d/eclipse/builds/20040121_1953-WB213-AD-V512D-00/eclipse/plugins/com.ibm.etools.j2ee.ui/build/pluginBuild/commonbld/com/ibm/etools/ejb/ui/presentation/EJBEditorOutlineContentProvider.class

>>> >     735 [main] unzip 1820 cmalloc: cmalloc returned NULL
>>> > error:  zipfile probably corrupt (segmentation violation)

>>> which I get even unzip'ing a known-good file (i.e. one that I
>>> unzip'ed successfully before upgrading from 1.5.5-1).

One more data point: just now I tried unzipping a new build, which a
colleague has unzipped using different tools. Unzip failed again,
slightly differently:

>   inflating: 
/d/eclipse/builds/20040210_1925-WB213-AD-V512D-W5/eclipse/plugins/com.ibm.etools.j2ee.ui/build/pluginBuild/commonbld/com/ibm/etools/ejb/ui/actions/CreateEJBRefAction.class 
 
>     657 [main] unzip 2244 cmalloc: cmalloc returned NULL
> error:  zipfile probably corrupt (segmentation violation)
> Archive:  /d/eclipse/zips/wsa-jdk-20040210_1925-WB213-AD-V512D-W5.zip

Failed in the same plugin? Anyway:

Thomas L Roche 02/11/2004 06:08 PM
>> it seems pretty clear to me that something "down deep" in the base
>> broke after 1.5.5-1:

>> 0 both character-mode (e.g. unzip) and X (e.g. emacs) apps are broken

>> 1 inputs that worked in 1.5.5-1 don't work now

>> 2 failures are intermittent and apparently random

>> 3 error messages suggest malloc problems 

>> Am I missing something?

Christopher Faylor Wed, 11 Feb 2004 18:45:42 -0500
> Actual debugging of the problem, with a debugger?

Arrgghh--lousy timing, but pain threshold is met. 2Q:

* Is there a debugging howto more {complete, up-to-date} than

http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/src/winsup/cygwin/how-to-debug-cygwin.txt?rev=1.9&content-type=text/plain&cvsroot=src

* Can someone provide directions (better yet, a script) for

http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/src/winsup/cygwin/how-to-debug-cygwin.txt?rev=1.9&content-type=text/plain&cvsroot=src
> 1.  First things first

>     The first thing you'll need to do is to build cygwin1.dll and
>     your crashed application from sources. To debug them you'll need
>     debug information, which is normally stripped from executables.
>     You probably also want to build a version of the dll with more
>     debugging capabilities by reconfiguring your build directory,
>     specifying the --enable-debugging option to configure.


--
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/



More information about the Cygwin mailing list