X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
X-Authority-Analysis:	v=1.0 c=1 a=VGbN3ngO2RUA:10 a=xe8BsctaAAAA:8 a=UnS7OIA5pbsSLh3IVTUA:9 a=yQ8RkJN69lWzSWfYJJR-NUCd1EAA:4 a=eDFNAWYWrCwA:10 a=rPt6xJ-oxjAA:10
Message-ID:	<47C80353.4040906@byu.net>
Date:	Fri, 29 Feb 2008 06:06:27 -0700
From:	Eric Blake <ebb9 AT byu DOT net>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com, Nigel DOT Hathaway AT ubiquisys DOT com
Subject:	Re: Problem with dev nodes in tar extract
References:	<094A73044298734FB7D58CAAA319E1D6BC4AD5 AT UBIQ-SERV1 DOT ubiquisys DOT local>
In-Reply-To:	<094A73044298734FB7D58CAAA319E1D6BC4AD5@UBIQ-SERV1.ubiquisys.local>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Nigel Hathaway on 2/29/2008 4:36 AM:
| I have created a gzipped compressed tar archive on Linux of an embedded
| Linux file system. It was compressed under Linux using fakeroot (so that
| everything is owned as root and dev nodes work).

Dev nodes are OS specific.  You will probably never get this to work,
because cygwin's notions of which major device numbers map to which
devices, while modeled after Linux, is not identical to Linux.  You are
trying to do something that is inherently non-portable.

| There error message I get is:
|
| 171 [main] tar 7900 _cygtls::handle_exceptions: Error while dumping
| state (probably corrupted stack)
|
| Segmentation fault (core dumped)

Obviously, it would be nicer if we didn't crash the cygwin syscall, but
this is not going to be my highest priority bug investigation.  Strace may
be helpful to you to find out what is going on just before the crash.  And
a simple, self-contained test case written in C will make it easier for
the cygwin development team to look into this, if it is really that
important to you (hint - pointing to tar's source code is not simple
enough for honing in on the cause of the crash).

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 AT byu DOT net
volunteer cygwin tar maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHyANS84KuGfSFAYARAtw4AJ9wpPzxaJX8lKuFrU+mWIK7ZxsUZgCgmzP0
dgeWrvdwmq2m1nUTUTa3768=
=Jso7
-----END PGP SIGNATURE-----

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