On Tue, Jan 03, 2006 at 07:51:25PM -0500, Igor Peshansky wrote: >On Tue, 3 Jan 2006, Christopher Faylor wrote: > >> On Fri, Dec 30, 2005 at 01:27:11AM -0500, Christopher Faylor wrote: >> >On Tue, Dec 27, 2005 at 11:38:46PM -0600, Tom Rodman wrote: >> >>Does the strace log hint at a solution? Is there any other test I >> >>might try that would help you debug this? >> > >> >The latest snapshot has better strace capabilities. Rather than trying >> >to munge your sshd service startup, please just start it as normal and, >> >from a privileged account, use "strace -ostrace.out -pNNNN" to capture >> >the output, where NNNN is the pid of the sshd process. You need to do >> >this from an account which has enough privileges to both find the sshd >> >process and to allow strace to access it. Either "ps -W" or taskman >> >should show the pid of the running sshd.exe. >> > >> >Please use the latest DLL and the latest version of strace.exe from the >> >snapshot: http://cygwin.com/snapshots/ >> >> Is there any movement on this? If multiple people can duplicate the >> problem I would think that we'd have at least one person posting strace >> results. > >Attached is the output of 'strace -f -p SSHD_PID' for ('uname -svr' = >'CYGWIN_NT-5.1 1.5.19(0.149/4/2) 2006-01-03 18:21'). Looks like the >spawned bash process dies with exception C0000142, and Cygwin is unable to >get the Windows exit code. Since the actual output is over 250k, I've >bzipped it.
That seems to be a kernel that you built yourself rather than a snapshot, is that correct? Can I assume that this is up-to-date with CVS? cgf -- 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/
