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
Date: Fri, 8 Aug 2003 13:35:49 -0400
From: Christopher Faylor <cgf-idd AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: What is the minimum needed to run gtar?
Message-ID: <20030808173549.GE9351@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3D5E0EA708C5DD44B7575859D366728C2DC29D AT svr-orw-exc-02 DOT wv DOT mentorg DOT com> <3F3150CF DOT 1F053532 AT acm DOT org> <16178 DOT 40732 DOT 673704 DOT 456513 AT phish DOT entomo DOT com> <3F33CBFD DOT E2C954C2 AT acm DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F33CBFD.E2C954C2@acm.org>
User-Agent: Mutt/1.4.1i

On Fri, Aug 08, 2003 at 09:12:45AM -0700, David Rothenberger wrote:
>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.

That's because it is currently broken.  There was a hack posted to get it
working.  I think it was to the cygwin mailing list.

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/