delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2001/10/04/09:37:52

Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: 4 Oct 2001 09:37:49 -0400
Message-ID: <20011004133749.13602.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Tar stackdump on bad mountpoint

With the current CVS repository....

1) Pick a drive letter that doesn't exist on your machine (I'll use
   "q:" in this example).

2) Run "mkdir -p /q/q".

3) Run "mount -s -b -x q: /q".

4) Run "tar --listed-incremental /tmp/foo --create --file /dev/null
   /q".  You'll get something like:

     tar: /q/q: Cannot stat: No such file or directory
     tar: Removing leading `/' from member names
     tar: Error exit delayed from previous errors

   So far so good.

5) Now run "tar --listed-incremental /tmp/foo --create --file
   /dev/null /cygdrive/c/cygwin/q" (assuming that your Cygwin is
   installed in c:/cygwin).  You'll get something like:

     tar: /cygdrive/c/cygwin/q/q: Cannot savedir: No such file or directory
     Segmentation fauilt (core dumped)

   This also happens if you mount c: as /c and use /c/cygwin/q
   instead of /cygdrive/c/cygwin/q.

I was unable, with the minimal effort for which I have time at the
moment, to get a useful stack trace out of the running tar when this
problem occurs.  I do not have any more time to investigate this
today, because I've got two stop-ship bugs in my own product that I
need to fix today on penalty of death :-).  I will investigate this
problem as soon as I possibly can (which, alas, may not be until next
Thursday, because of the bugs I need to fix here and because I'll be
out Tuesday and Wednesday of next week), but in the meantime, I wanted
to give a heads up because I know there were mumblings about releasing
1.3.4 and it may need to be held up because of this.

Sorry I can't help more right away....

  jik

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019