| delorie.com/archives/browse.cgi | search |
On Thu, May 11, 2000 at 12:20:11PM -0500, Mumit Khan wrote: >Can someone check if the problem goes away with thread-disabled Cygwin >DLL? Note that in my case it's hanging in munmap (unless it's also >popping up a window on the local box, which I can't see when logged on >remotely, sigh), which may point to a Cygwin waiting on a lock. Cygwin >currently uses a single resource lock, even though the basic framework >for using multiple locks is there via LOCK_ macros, so a single mismatched >Set/Release lock may cause problems. I can't check currently since I'm >connecting to my home net via modem, and don't have gcc on my laptop. I don't understand. If gcc is hung waiting for a resource lock, that will be made very clear by attaching gdb to the hung process. I don't see why we have to go the the pain of attempting a rebuild of cygwin as a debugging technique. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |