Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 12 Aug 2005 20:02:09 +0300 Message-Id: From: Eli Zaretskii To: rms AT gnu DOT org CC: jbuehler AT spirentcom DOT com, emacs-devel AT gnu DOT org, emacs_user AT hotmail DOT com, cygwin AT cygwin DOT com In-reply-to: (rms@gnu.org) Subject: Re: is there a cygwin maintainer for gnu emacs? Reply-to: Eli Zaretskii References: <42F9E707 DOT 1030302 AT spirentcom DOT com>

<42FB6AF2 DOT 2060301 AT spirentcom DOT com> > From: "Richard M. Stallman" > CC: eliz AT gnu DOT org, emacs-devel AT gnu DOT org, emacs_user AT hotmail DOT com, > cygwin AT cygwin DOT com > Date: Fri, 12 Aug 2005 10:59:49 -0400 > > 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. > > Until the bug is debugged, we know nothing about where the cause lies. That's true, but it should have been clear that it's not a SEGV, since Emacs says something like "Abort (core dumped)", which clearly tells that it got SIGABRT, not SIGSEGV. So, while Emacs doesn't say that it happened within GC, it does tell that it committed suicide (aborted), not hit a SIGSEGV. -- 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/