ash stackdump in cygwin 1.3.3-2
Christopher Faylor
cgf@redhat.com
Thu Nov 15 13:25:00 GMT 2001
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/
More information about the Cygwin
mailing list