GetModuleFileName() hang during signal processing
Joe Buehler
jbuehler@hekimian.com
Tue Apr 1 15:49:00 GMT 2003
The problem I have been chasing appears to be a hang calling
GetModuleFileName() in interruptible() in exceptions.cc.
In the cases where this works, the address passed to the function
is a pointer at user DLL data. In the case of the hang,
it is a pointer at ntdll.dll data.
This is with NT4 SP5. Any suggested workarounds? For the moment,
I am going to try forcing "not interruptible" when in Microsoft
DLL address range (for NT anyway).
--
Joe Buehler
409 6517151 [sig] ksh 480 setup_handler: suspending mainthread 0x1CC
320 6517471 [sig] ksh 480 setup_handler: checking mutos
332 6517803 [sig] ksh 480 setup_handler: check 0x610E6C90
330 6518133 [sig] ksh 480 setup_handler: check 0x610E559C
274 6518407 [sig] ksh 480 setup_handler: check 0x610E4704
273 6518680 [sig] ksh 480 setup_handler: check 0x610E3A4C
310 6518990 [sig] ksh 480 setup_handler: check 0x610E38C4
286 6519276 [sig] ksh 480 setup_handler: check 0x610E4FA8
291 6519567 [sig] ksh 480 setup_handler: check 0x610E35CC
361 6519928 [sig] ksh 480 setup_handler: check 0x610E49C4
257 6520185 [sig] ksh 480 setup_handler: check 0x610E551C
247 6520432 [sig] ksh 480 setup_handler: check mainthread.frame
159 6520591 [sig] ksh 480 setup_handler: getting thread context 0x1CC iam 0xE4
272 6520863 [sig] ksh 480 setup_handler: got thread context
141 6521004 [sig] ksh 480 setup_handler: check priority
131 6521135 [sig] ksh 480 setup_handler: check th
123 6521258 [sig] ksh 480 setup_handler: checking interruptible
129 6521387 [sig] ksh 480 interruptible: interruptible()
174 6521561 [sig] ksh 480 interruptible: about to call GetModuleFileName(0x77F60000, 0x90F840, 20)
More information about the Cygwin-developers
mailing list