Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 17 Nov 2000 16:00:57 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: XEmacs on cygwin wierdness Message-ID: <20001117160057.B17114@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3A0F9044.2E387F2F@ece.gatech.edu> <20001113115212.I7424@redhat.com> <3A10962B.1D0A386E@ece.gatech.edu> <20001113212846.B23184@redhat.com> <3A10B52B.47FFF093@ece.gatech.edu> <20001113225846.A27122@redhat.com> <3A121018.CAA2139D@ece.gatech.edu> <3A123D94.90D09BD4@ece.gatech.edu> <20001116154956.B23051@redhat.com> <64164781463.20001117093033@logos-m.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@redhat.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@sourceware.cygnus.com