>>>>> Christopher Faylor writes: > The latest snapshot has been uploaded. > If you have been asked to test a snapshot, please try this one. It contains > additional debugging which may help track down the "Xemacs problem".
> The error messages will be going to stderr, so if possible redirect the > output to a file for capture. I haven't got Xemacs or rxvt in the defunct state yet, but starting rxvt or ps/procps/pstree gives: CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 Starting xterm from an rxvt window gives: In the Rxvt window CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 CloseHandle(*h) failed _onreturn::~_onreturn():1102 In the Xterm window 587214 [main] xterm 296 modify_handle: virtual void fhandler_pipe::set_close_on_exec(bool):175 handle guard<0x680> not found Will follow up, when one of the process go to defunct state. Ciao Volker -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/