X-Spam-Check-By: sourceware.org Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <20060223112040.GD31794@calimero.vinschen.de> References: <00fc01c6371d$789be620$a501a8c0 AT CAM DOT ARTIMI DOT COM> <897AB4F9-DECD-4714-8C45-5DA39C096F99 AT rehley DOT net> <20060223112040 DOT GD31794 AT calimero DOT vinschen DOT de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4BFEBADC-51DD-40CD-9595-9337ABCBDD8E@rehley.net> Content-Transfer-Encoding: 7bit From: Peter Rehley Subject: Re: Hanging at GetModuleFileName in inside_kernel function Date: Thu, 23 Feb 2006 08:19:41 -0800 To: cygwin AT cygwin DOT com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi, On Feb 23, 2006, at 3:20 AM, Corinna Vinschen wrote: > On Feb 21 13:56, Peter Rehley wrote: >> On Feb 21, 2006, at 11:31 AM, Dave Korn wrote: >> >>> On 21 February 2006 19:06, Peter Rehley wrote: >>> >>>> Hi, >>>> >>>> Well, for my particular hang issue cygwin is hanging inside the >>>> inside_kernel function on the GetModuleFileName call. I tracked >>>> this >>>> down by adding debug statements (strace.prntf) until I got to the >>>> point where the debug print before GetModuleFileName would >>>> appear and >>>> the ones after it didn't. This is consistent. Each hang is >>>> happening >>>> at this spot. >>>> >>>> However, this doesn't explain what is happening, but only where. >>>> >>>> I also observed that the times it hung were the only times >>>> inside_kernel was actually called. >>>> >>>> I'm still trying to get more information. >>>> Peter >>>> >>>> p.s. using cygwin snapshot 1.5.19-20060205. > > Due to your problem report and some googling, I had some vague idea > yesterday, what the problem could be. But it's not clear if the very > simple patch I applied yesterday does really change anything with > respect to your problem. > > Please test the 2006-02-22 snapshot from http://cygwin.com/snapshots/ > and report if you see a change, to the good or to the bad. > > Yeah, I saw that change, and I tried yesterdays snapshot but it still hung. I also did some more googling and found that someone submitted a patch a few years ago. The patch checked to see if it was inside the ntdll.dll by looking at the handle. http://www.cygwin.com/ml/cygwin-patches/2003-q2/msg00004.html I found this google too. http://blogs.msdn.com/oldnewthing/archive/2004/01/28/63880.aspx I'm going to try that patch today and see what happens. Christopher didn't apply it because it was a bandage and didn't really fix the bigger problem. Peter -- 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/