Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Tue, 4 Sep 2001 13:02:37 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Cc: cwilson AT ece DOT gatech DOT edu
Subject: Re: cygwin 1.3.3 announcment -- extra words solicited
Message-ID: <20010904130237.B7509@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com, cwilson AT ece DOT gatech DOT edu
References: <999380998 DOT 30841 DOT ezmlm AT sources DOT redhat DOT com> <3B92D324 DOT 9030308 AT ece DOT gatech DOT edu> <3B92EC8F DOT 3070605 AT ece DOT gatech DOT edu> <20010902224411 DOT A21914 AT redhat DOT com> <3B92F0CF DOT 4040101 AT ece DOT gatech DOT edu> <3B9313A1 DOT 4010200 AT ece DOT gatech DOT edu> <20010903013236 DOT A22505 AT redhat DOT com> <3B943067 DOT 5000207 AT ece DOT gatech DOT edu> <4679657631 DOT 20010904104946 AT logos-m DOT ru> <3B950586 DOT 3050106 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B950586.3050106@ece.gatech.edu>
User-Agent: Mutt/1.3.21i

On Tue, Sep 04, 2001 at 12:47:02PM -0400, Charles Wilson wrote:
>egor duda wrote:
>
>>
>>CW> Well, I don't think I can really figure out what the problem is unless 
>>I CW> know what program make is trying to execute in the exec_command() 
>>CW> function -- but that data doesn't show up in the stackdump.  OTOH, I 
>>CW> can't just step through the entire build waiting for the crash -- it 
>>CW> does not appear deterministic.
>>
>>CW> Should I build dumper.exe and try the JIT functionality?  would that 
>>help?
>>
>>it would be enough (and probably easier) to use JIT debugging with
>>gdb. adding 'error_start=x:\path\to\gdb\gdb.exe' to CYGWIN environment
>>variable should do.
>
>
>Okay, I did this -- but I got this error (instead of the 'expected' one 
>I reported earlier):
>
>make[2]: Leaving directory 
>`/usr/src/cygwin/obj/i686-pc-cygwin/winsup/cinstall'
>      0 [main] make 1640 handle_exceptions: Error while dumping state 
>(probably
>corrupted stack)
>Signal 11
>make[1]: *** [subauth] Error 139
>make[1]: Leaving directory `/usr/src/cygwin/obj/i686-pc-cygwin/winsup'
>make: *** [all-target-winsup] Error 2
>
>And when gdb popped up, it had no state data from the crashed process. 
>(e.g. it was as if I'd merely typed "gdb make" ).  What should I do next?

Make sure you do a:
thread 1
bt

If that still doesn't show anything, then:

p /x $esp
x/40x $esp

Then we can laboriously inspect the stack to see if something got clobbered.

Btw, Chuck, is there some reason why you are just subscribed to the digest
version?  I keep forgetting to Cc you.

cgf