Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 23 Nov 2001 23:15:09 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ash stackdump in cygwin 1.3.3-2 Message-ID: <20011124041509.GA22258@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3BCB0DE8 DOT 2050006 AT milohedge DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BCB0DE8.2050006@milohedge.com> User-Agent: Mutt/1.3.23.1i On Mon, Oct 15, 2001 at 05:25:12PM +0100, Robert Bogomip wrote: >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. This should be fixed in the latest cygwin snapshot. cgf -- 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/