From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joe Buehler Newsgroups: gmane.os.cygwin,gmane.emacs.devel Subject: Re: is there a cygwin maintainer for gnu emacs? Date: Thu, 11 Aug 2005 11:12:50 -0400 Message-ID: <42FB6AF2.2060301@spirentcom.com> References: <42F9E707.1030302@spirentcom.com> Reply-To: jbuehler@spirentcom.com NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1123773233 24272 80.91.229.2 (11 Aug 2005 15:13:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 11 Aug 2005 15:13:53 +0000 (UTC) Cc: Eli Zaretskii , emacs_user@hotmail.com, cygwin@cygwin.com, emacs-devel@gnu.org Original-X-From: cygwin-return-111635-goc-cygwin=m.gmane.org@cygwin.com Thu Aug 11 17:13:50 2005 Return-path: Original-Received: from sourceware.org ([12.107.209.250]) by ciao.gmane.org with smtp (Exim 4.43) id 1E3Ek2-0000iZ-6A for goc-cygwin@gmane.org; Thu, 11 Aug 2005 17:13:10 +0200 Original-Received: (qmail 16768 invoked by alias); 11 Aug 2005 15:12:59 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Original-Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Original-Received: (qmail 16713 invoked by uid 22791); 11 Aug 2005 15:12:54 -0000 Original-Received: from host-64-47-34-180.masergy.com (HELO minotaur.hekimian.com) (64.47.34.180) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 11 Aug 2005 15:12:54 +0000 Original-Received: from [127.0.0.1] (jbuehler-xp.ad.spirentcom.com [10.32.15.30]) by minotaur.hekimian.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NMPCB32S; Thu, 11 Aug 2005 11:10:49 -0400 X-Sybari-Trust: af80e411 24a46624 0888bd50 0000013d User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) Original-To: rms@gnu.org In-Reply-To: Xref: news.gmane.org gmane.os.cygwin:67871 gmane.emacs.devel:41919 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:41919 Richard M. Stallman wrote: > 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. > > It would also not be very useful, since any info we could put into > such an error message could be quickly discovered by a little > investigation with a debugger. I have to disgree with that, it's the instant gut ueber-programmer reaction to such problems. Currently the user just gets an exiting emacs, leaving me with no clue as to why emacs exited. I then have to provide instructions to the user as to how to run the $*&$%#!!! debugger to help me figure out what happened. The debugger that he may or may not have installed, and may or may not even be ABLE to install. A simple last-ditch printf that says "corruption detected during garbage collection, see you later" would be a much easier way to get an initial handle on what the heck the problem is. As it was, without any message, my initial suspicion was a SEGV or similar, which would be much more likely to be a Cygwin problem than an emacs problem. -- Joe Buehler