Re: howto debug unzip under cygwin?

> 0 how to set GDB to catch unzip problems like

I'm afraid I'm not much of a gdb guru--"run" and "backtrace" when it
crashes is about the limit of my knowledge.

> 1 who's the maintainer(s) for the Cygwin port of unzip, and how to
>   contact her/him/them?

No clue.  (Presumably someone at Red Hat.)

> Actually that was there, already: the problem was stripping. 4 years
> of Java, 2 years of Perl, and I have totally forgotten the thrill of
> linkage :-( For future reference by the next poor bastard in my
> situation, what I did to see symbols in gdb was

Oops, yes, I should have thought of that, too.  I stopped stripping
things long ago, though, so it's fallen off my radar screen.

>   Note that the above was not enough, there was also

>> # INSTALL_PROGRAM = install -s -m $(BINPERMS)
>> INSTALL_PROGRAM = install -m $(BINPERMS)

Boy, they really want those binaries stripped. :-)  Makes sense,
though, considering the size of the whole Cygwin download...

>>> * where should I look for the underlying malloc code (cygwin1.dll?
>>>   libc*?), and how should I build/debug that?

>> No clue.  The Cygwin folks will have to answer that.

> OK, but they're list is very-high-volume, and they're not (in my
> humble experience) the most helpful lot. Is there a maintainer for the
> Cygwin port of unzip whom I could contact?

There may not be a Cygwin-unzip maintainer, per se.  In any case, the
fact that they've (apparently) acknowledged some sort of core problem
between the previous version and this one suggests that they're working
on it already and may be a little more responsive.  I really don't know
what else to say about it; I'm neither a Cygwin guru nor a Win32 guru.

Greg