Mail Archives: cygwin/2003/08/08/12:13:04
David Rothenberger wrote:
>
> David Rothenberger writes:
> > "Biederman, Steve" wrote:
> > >
> > > I want to allow the users I support to be able to run Cygwin tar on their Windows machines.
> > > These machines have not had any Cygwin installed; they're just bare Windows machines.
> > >
> > > I provided them tar.exe and cygwin1.dll and assumed that with these, they could run
> > > Cygwin tar sucessfully. It appears that that isn't the case: machines without Cygwin
> > > installed see different behavior than machines which have it installed. (Running tar
> > > on machines without Cygwin installed creates incorrect tar archives.)
> >
> [snip]
> > Through experimentation, I discovered that the problem went away if I
> > created an /etc mount.
>
> I did a little debugging on this. It turns out that when tar
> "hangs", the process is in an infinite loop in malloc_consolidate().
Some googling uncovered that loops in malloc_consolidate() are usually a
sign of heap corruption. More googling suggested that compiling the
cygwin dll with --enable-malloc-debugging would be helpful for finding
heap corruption. But, I'm have quite a bit of trouble getting the dll
to compile with that configure switch.
I'm hacking and slashing my way through the compilation, but I'm
wondering whether it's worth it. Should I expect the malloc debugging
to work at all? Or is this something that worked in the past but hasn't
been tried in a long time and is probably no longer working?
Dave
--
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 -