public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* ash stackdump in cygwin 1.3.3-2
@ 2001-10-15  9:25 Robert Bogomip
  2001-11-15 13:25 ` Christopher Faylor
  0 siblings, 1 reply; 3+ messages in thread
From: Robert Bogomip @ 2001-10-15  9:25 UTC (permalink / raw)
  To: cygwin

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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: ash stackdump in cygwin 1.3.3-2
  2001-10-15  9:25 ash stackdump in cygwin 1.3.3-2 Robert Bogomip
@ 2001-11-15 13:25 ` Christopher Faylor
  2001-11-23 20:14   ` Christopher Faylor
  0 siblings, 1 reply; 3+ messages in thread
From: Christopher Faylor @ 2001-11-15 13:25 UTC (permalink / raw)
  To: cygwin

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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: ash stackdump in cygwin 1.3.3-2
  2001-11-15 13:25 ` Christopher Faylor
@ 2001-11-23 20:14   ` Christopher Faylor
  0 siblings, 0 replies; 3+ messages in thread
From: Christopher Faylor @ 2001-11-23 20:14 UTC (permalink / raw)
  To: cygwin

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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-11-24  4:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-15  9:25 ash stackdump in cygwin 1.3.3-2 Robert Bogomip
2001-11-15 13:25 ` Christopher Faylor
2001-11-23 20:14   ` Christopher Faylor

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).