On Tue, 14 Oct 2003, Christopher Faylor wrote: > So it must not really be cygpath that is hanging, then. The stack trace that > you provided was more likely for an execed bash stub. You could try setting > CYGWIN_DEBUG=bash to test that theory. > Considering these things (cygpath, strace, etc.) only hang under /bin/bash and not /bin/sh, I'd say that is likely.
Once again, I'll test ASAP, but I'm swamped right now. > >> The stack trace below is from a process that is running cygpath not > >> from cygpath itself. > >> > >Ok. That is what it looked like to me too, but I don't know how the > >Cygwin "fork exec" stuff works yet (spawn_guts is huge), so I wasn't > >entirely sure. > > > >Maybe I was just too rushed, but I'm almost positive I attached to > >the only thing ps -ef said was cygpath. Why does the spawner (bash?) say > >it's cygpath? > > The name of the stub changes when it execs a process. It goes something > like this: > Thanks for the hand hold. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/
