Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 10 Aug 2005 20:56:02 +0300 Message-Id: From: Eli Zaretskii To: jbuehler@spirentcom.com CC: emacs_user@hotmail.com, cygwin@cygwin.com, emacs-devel@gnu.org In-reply-to: <42F9E707.1030302@spirentcom.com> (message from Joe Buehler on Wed, 10 Aug 2005 07:37:43 -0400) Subject: Re: is there a cygwin maintainer for gnu emacs? Reply-to: Eli Zaretskii References: <42F9E707.1030302@spirentcom.com> > Date: Wed, 10 Aug 2005 07:37:43 -0400 > From: Joe Buehler > Cc: ehud@unix.mvs.co.il, cygwin@cygwin.com, emacs-devel@gnu.org > > I would think that emacs would say why it is aborting. When GC encounters a fatal inconsistency in the Emacs data structures, it is generally unsafe to say anything, since that could easily cause a nested fatal signal. > Is there an expert on the emacs internals that would care to comment > on what this abort might mean? I'm not sure I'm such an expert on this, but the file etc/DEBUG has a special section on debugging crashes inside GC. I don't think there's a general recipe, one just needs to follow the advice in etc/DEBUG and find out the corrupted data structure. Once the bad data structure is found, the next step is to trace its life cycle and find what piece of code corrupted it. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/