Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Fri, 17 Nov 2000 16:00:57 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: XEmacs on cygwin wierdness
Message-ID: <20001117160057.B17114@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <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> <20001116154956 DOT B23051 AT redhat DOT com> <64164781463 DOT 20001117093033 AT logos-m DOT ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <64164781463.20001117093033@logos-m.ru>; from deo@logos-m.ru on Fri, Nov 17, 2000 at 09:30:33AM +0300

On Fri, Nov 17, 2000 at 09:30:33AM +0300, Egor Duda wrote:
>Hi!
>
>Thursday, 16 November, 2000 Christopher Faylor cgf AT redhat DOT com wrote:
>
>>>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.
>
>CF> That sounds like Xemacs is either forking or execing a new process.  That
>CF> would also explain why main_environ had "stuff" in it but now why environment
>CF> handling was getting confused.
>
>CF> Was there any further resolution on this, Chuck?  One other thing you can do
>CF> is 'set CYGWIN=error_start_init=x:\path\to\gdb.exe' to have cygwin start gdb
>CF> automatically when an error occurs.
>
>'set CYGWIN=error_start=x:\path\to\gdb.exe' actually :)

Oops.  Right.  Sorry.

cgf

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