Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3BCB0DE8.2050006@milohedge.com>
Date:	Mon, 15 Oct 2001 17:25:12 +0100
From:	Robert Bogomip <bob DOT bogo AT milohedge DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5) Gecko/20011011
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	cygwin <cygwin AT cygwin DOT com>
Subject:	ash stackdump in cygwin 1.3.3-2

There's a problem with sh's default PATH. Using bash's "exec -c" builtin
to run a command with no environment:

   bash-2.05$ (exec -c sh -c 'export PATH; ls')
         0 [main] sh 8724 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
   bash-2.05$

It's the "export" that seems to cause the problem:

   bash-2.0.5$ (exec -c sh)
   $ set
   PS1=$
   PS2=>
   PATH=/bin:/usr/bin
   IFS=
   $ export PATH
   $ ls
       0 [main] sh 8840 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
   $

Hmmm.
-- 
Robert Bogomip /// mailto:bob.bogo at milohedge.com
Milo Hedge Ltd, OCFI, Mill Street, Oxford, OX2 0JX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -