delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/02/11/23:15:37

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Subject: debugging unzip, was: unzip problem after upgrading
From: Thomas L Roche <tlroche AT us DOT ibm DOT com>
Message-ID: <OFB7EE0ECE.4B88CDD1-ON85256E38.0016B735-85256E38.00174BB1@us.ibm.com>
Date: Wed, 11 Feb 2004 23:14:26 -0500

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?

Fortunately, useful help arrives:

Igor Pechtchanski 02/11/2004 09:20:22 PM:
> Make sure you have the "tar", "patch", "gcc", "gcc-g++", "gdb", and
> "make" packages installed (via Cygwin's setup).

> Download the unzip source (e.g., "wget ftp://mirrors.rcn.
> net/pub/sourceware/cygwin/release/unzip/unzip-5.50-5-src.tar.bz2").

> Untar the unzip source to /usr/src (e.g., "tar -C /usr/src -xjf
> unzip-5.50-5-src.tar.bz2").

> Enter that directory and run the prep, conf, build, and install
> steps of the script (e.g., "cd /usr/src && ./unzip-5.50-5.sh prep &&
> . /unzip-5.50-5.sh conf && ./unzip-5.50-5.sh build &&
> ./unzip-5.50-5.sh install").

> You should now have a debug build of unzip sitting in
> /usr/src/unzip-5.50/.inst (the maintainer graciously set it up to
> build with debugging by default)

more below

> Enter that directory and run gdb: "cd /usr/src/unzip-5.50/.inst && gdb
> --args ./unzip failing_zip_file"

almost: ./usr/bin/unzip.exe

I do

wget -O - 
ftp://mirrors.rcn.net/pub/sourceware/cygwin/release/unzip/unzip-5.50-5-src.tar.bz2 
| tar -C /usr/src -xj
cd /usr/src && ./unzip-5.50-5.sh prep && ./unzip-5.50-5.sh conf && 
./unzip-5.50-5.sh build && ./unzip-5.50-5.sh install
cd /usr/src/unzip-5.50/.inst && gdb --args ./usr/bin/unzip.exe 
/d/eclipse/zips/wsa-jdk-20040210_1925-WB213-AD-V512D-W5.zip

and get

> GNU gdb 2003-09-20-cvs (cygwin-special)
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you 
are
> welcome to change it and/or distribute copies of it under certain 
conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for 
details.
> This GDB was configured as "i686-pc-cygwin"...(no debugging symbols 
found)...

Igor Pechtchanski 02/11/2004 09:20:22 PM:
> Set a breakpoint at the failing line (fileio.c, line 146) and start 
> debugging :-)

I do

(gdb) break fileio.c:146

> No symbol table is loaded.  Use the "file" command.

(gdb) file ./usr/bin/unzip.exe

> Reading symbols from ./usr/bin/unzip.exe...(no debugging symbols 
found)...done.

This sounds bad: if so, how to tweak the script above to include
debugging?


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019