Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
Date: Thu, 16 Nov 2000 15:49:56 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: XEmacs on cygwin wierdness
Message-ID: <20001116154956.B23051@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3A0F827C DOT 15675931 AT ece DOT gatech DOT edu> <20001113010018 DOT A6535 AT redhat DOT com> <3A0F9044 DOT 2E387F2F AT ece DOT gatech DOT edu> <20001113115212 DOT I7424 AT redhat DOT com> <3A10962B DOT 1D0A386E AT ece DOT gatech DOT edu> <20001113212846 DOT B23184 AT redhat DOT com> <3A10B52B DOT 47FFF093 AT ece DOT gatech DOT edu> <20001113225846 DOT A27122 AT redhat DOT com> <3A121018 DOT CAA2139D AT ece DOT gatech DOT edu> <3A123D94 DOT 90D09BD4 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <3A123D94.90D09BD4@ece.gatech.edu>; from cwilson@ece.gatech.edu on Wed, Nov 15, 2000 at 02:39:00AM -0500

On Wed, Nov 15, 2000 at 02:39:00AM -0500, Charles Wilson wrote:
>"Charles S. Wilson" wrote:
>> 
>> Christopher Faylor wrote:
>> >
>> > The more I think about this, the more I think that your stack trace
>> > should actually be impossible.  It looks like a pointer that should be
>> > zero isn't.  Out of curiousity, does the patch below cause any
>> > difference?
>> 
>> Yes, that fixes it.  Now I can run xemacs (without recompiling *it*)
>> from cmd.exe or from bash.  No problems. However, obviously there is
>> something wacky going on with xemacs; unfortunately, I don't understand
>> the wacky structure of xemacs.exe well enough to debug it
>> authoritatively.
>> 
>> I'll give it a shot and report back....
>
>Well, I'm not sure why, but I can't single-step XEmacs and gdb doesn't
>recognize any breakpoints prior to the bomb.  I can only "run" and then
>investigate after the crash.

That sounds like Xemacs is either forking or execing a new process.  That
would also explain why main_environ had "stuff" in it but now why environment
handling was getting confused.

Was there any further resolution on this, Chuck?  One other thing you can do
is 'set CYGWIN=error_start_init=x:\path\to\gdb.exe' to have cygwin start gdb
automatically when an error occurs.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com