delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/08/11/10:29:38

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Richard M. Stallman" <rms AT gnu DOT org>
To: Eli Zaretskii <eliz AT gnu DOT org>
CC: jbuehler AT spirentcom DOT com, emacs_user AT hotmail DOT com, cygwin AT cygwin DOT com,
emacs-devel AT gnu DOT org
In-reply-to: <ull39oevh.fsf@gnu.org> (message from Eli Zaretskii on Wed, 10 Aug 2005 20:56:02 +0300)
Subject: Re: is there a cygwin maintainer for gnu emacs?
Reply-to: rms AT gnu DOT org
References: <BAY107-F29E79AE5E6EDDEC1D619EBF8BA0 AT phx DOT gbl> <42F9E707 DOT 1030302 AT spirentcom DOT com> <ull39oevh DOT fsf AT gnu DOT org>
Message-Id: <E1E3E1X-0003e9-Kh@fencepost.gnu.org>
Date: Thu, 11 Aug 2005 10:27:11 -0400

    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.

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019