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
Message-ID:	<010e01c32b87$dda40880$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	<cygwin AT cygwin DOT com>, "Soren Andersen" <somian AT adelphia DOT net>
References:	<20030605172020 DOT GG7542 AT ny-kenton2a-710 DOT buf DOT adelphia DOT net>
Subject:	Re: Cygwinperl & tar on Win9x (really tar)
Date:	Thu, 5 Jun 2003 18:28:22 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1165
X-Cam-ScannerAdmin:	mail-scanner-support AT ucs DOT cam DOT ac DOT uk
X-Cam-AntiVirus:	Not scanned
X-Cam-SpamDetails:

Soren Andersen wrote:
> Hello Cygwinauts,
>
> I'd like to report a problem I encountered recently try to run CPAN(.pm)
> on Cygwinperl to ... you know what CPAN does.
>
> My system is Win98 and I suspect from absence of reports concerning this
> that somehow this isn't affecting people on other-derived M$ Windows
> platforms. All of this is vis a vis cygwin on these platforms, of
> course.
>
> CPAN fails to be able to make or install modules because the system call
> to tar(1) returns an error (generates a SIGSEGV [?] signal) when perl
> tries to have tar unroll a module archive. On examination, tar is being
> called by perl code in the innards of CPAN.pm, with the old-style flags
> (switches) un-prefaced by a hyphen/dash/(-) token, e.g.:
>
>    $ tar xvf foo.tar
>
> On testing, the stackdump can be caused by manually passing arguments
> (flags, switches) to tar(1) without a hyphen. I myself always habitually
> use the modern GNU-style with tar, i.e. "$ tar -xvzf foo.tar.gz" when I
> run `tar' manually or use it in scripts, so this bug never bit me before
> CPAN showed it to me.
...
> Also, sorry, I am composing this message from Debian GNU/Linux, so I
> have not the opportunity to generate a "cygcheck.exe" output file to
> attach to this message. My `tar' was from cygwin release 1.13.25 and
> then I reverted to the previous one (whatever that was). Both tar
> versions manifested the same segfault.

I habitually use the old-style options, and have never encountered a
segfault - but I'm using WinXP.

I suggest you ensure that all your packages are up to date, and ensure you
really are running Cygwin's tar.
If the segfault persists, try reinstalling the cygwin and tar packages.

If still no luck, you could try a full reinstall of Cygwin, or debugging the
segfault by using gdb on an unstripped version of tar.



Max.


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