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: Fri, 12 Aug 2005 20:02:09 +0300 Message-Id: From: Eli Zaretskii To: rms@gnu.org CC: jbuehler@spirentcom.com, emacs-devel@gnu.org, emacs_user@hotmail.com, cygwin@cygwin.com In-reply-to: (rms@gnu.org) Subject: Re: is there a cygwin maintainer for gnu emacs? Reply-to: Eli Zaretskii References: <42F9E707.1030302@spirentcom.com> <42FB6AF2.2060301@spirentcom.com> > From: "Richard M. Stallman" > CC: eliz@gnu.org, emacs-devel@gnu.org, emacs_user@hotmail.com, > cygwin@cygwin.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/