On Fri, Apr 05, 2002 at 08:22:26PM -0500, Harold Hunt wrote: >Oh yeah, by "sketchy" I meant that after it happens a few times and I >switch the focus away from Cygwin/XFree86 two things happen: > >1) Cygwin/XFree86 freezes solid. > >2) The Windows mouse cursor disappears and the Windows mouse doesn't >work until I reboot. The mouse doesn't even start to work again when >you press Ctrl+Alt+Del and get the Windows Security box that usually >works perfectly even when programs have crashed. > >Yeah... that's pretty sketchy.
It sounds like typical memory overwrite problems. I have never seen that error show up in any other application. I thought I had actually turned off assertions in the released version of cygwin. Guess I was mistaken. There are only two popular users of vfork that I'm aware of: sh and make. It's possible that their needs are simple enough that they're not triggering a cygwin bug that kde is triggering. It's also possible that kde is just doing a plain old fashioned overwriting of memory. It should be fairly simple to figure out what's stomping on the memory but it will have to (obviously?) be done by someone who has kde and feels up to debugging the cygwin DLL. Just watching what happens to cygheap->fdtab.fds_on_hold during a vfork should pinpoint it pretty quickly. 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/
