This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: ash stackdump in cygwin 1.3.3-2
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 23 Nov 2001 23:15:09 -0500
- Subject: Re: ash stackdump in cygwin 1.3.3-2
- References: <3BCB0DE8.2050006@milohedge.com>
- Reply-to: cygwin at cygwin dot com
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/