X-Spam-Check-By: sourceware.org
Message-ID: <4405E152.9040302@steeleye.com>
Date: Wed, 01 Mar 2006 13:00:50 -0500
From: Paul Clements <paul DOT clements AT steeleye DOT com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Hanging at GetModuleFileName in inside_kernel function
References: <000301c638a4$dfc6fd70$a501a8c0 AT CAM DOT ARTIMI DOT COM> <10C8EE35-B5B3-40CD-B9EA-122E2CB26343 AT rehley DOT net> <20060224022745 DOT GA7541 AT trixie DOT casa DOT cgf DOT cx> <D4E4BB12-5980-4659-8A84-796120AC20B9 AT rehley DOT net> <20060228200154 DOT GA19419 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20060228200154.GA19419@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Christopher Faylor wrote:
> On Tue, Feb 28, 2006 at 11:10:05AM -0800, Peter Rehley wrote:

>>It seems like an improvement.  It didn't hang, but after about 4000  
>>iterations of the test script it got a segmentation fault.  It ran  
>>for 12 hours with another configure script in a separate window or  
>>about 11 hours and 45 minutes longer than before.  This is with the  
>>20060227 snapshot.
>>
>>Attached is the stackdump.

> ...which is a stackdump deep within bash itself, pretty far from any
> cygwin functions.

Just a point of interest here (maybe). I'm also seeing segfaults, but 
I'm running ksh (see thread: "shells hang during script execution"). 
Anyway, I just noticed that the last stack address (which looks bogus), 
as well as the EBP register value, are the same in the stack traces that 
both Peter and I posted:

Stack trace:
Frame     Function  Args
0022E848  0022FBFC  (00484660, 00000000, 0009C05C, 0041E1F2)

Leading up to this are all pdksh functions:

40ab39 expand (after call to waitlast)
40a0fa evalstr
40cfa8 comexec
[...]

(in Peter's stack trace, these were all bash functions)

It would seem very coincidental for these two crashes not to be related 
somehow.

Peter, any chance you could maybe list the function names (in bash) that 
lead up the stack to this? Perhaps there's some common function that is 
causing this?

Thanks,
Paul


--
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/