This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: GetModuleFileName() hang during signal processing
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 10 Apr 2003 01:34:55 -0400
- Subject: Re: GetModuleFileName() hang during signal processing
- References: <3E89DB14.1010105@hekimian.com> <20030402225120.GB9668@redhat.com>
- Reply-to: cygwin-developers at cygwin dot com
On Wed, Apr 02, 2003 at 05:51:20PM -0500, Christopher Faylor wrote:
>On Tue, Apr 01, 2003 at 01:31:48PM -0500, Joe Buehler wrote:
>>Checking the address range in interruptible() to prevent the call
>>to GetModuleFileName() does indeed fix the ksh93 hang problem.
>
>I'm sorry to say that this doesn't really "fix" the problem. You
>should be able to call GetModuleFileName without it hanging. I
>don't understand why it is hanging. Is there anything on google
>or in MSDN which would suggest that this is possible?
>
>Also, if this is repeatedly happening, that would suggest that one of
>cygwin's blocking calls is not being properly protected with a sigframe.
>See "how-signals-work.txt" for more details.
Whatever happened with this problem? Was this actually the thread
memory exhaustion problem mentioned in other messages?
cgf