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 09:30:33 +0300
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <cygwin AT sources DOT redhat DOT com>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <64164781463.20001117093033@logos-m.ru>
To: cygwin AT sources DOT redhat DOT com
Subject: Re: XEmacs on cygwin wierdness
In-reply-To: <20001116154956.B23051@redhat.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> <20001116154956 DOT B23051 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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 :)

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19



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