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: Sat, 13 Sep 2003 13:29:40 -0400 From: Christopher Faylor To: cygwin-xfree@cygwin.com, cygwin@cygwin.com Subject: Re: Still getting Signal 11 error msg Message-ID: <20030913172940.GB21878@redhat.com> Reply-To: cygwin-xfree@cygwin.com, cygwin@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com, cygwin@cygwin.com References: <000b01c37a18$e7689360$9e7b2852@leper> <3F6350C4.5030000@msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F6350C4.5030000@msu.edu> User-Agent: Mutt/1.4.1i On Sat, Sep 13, 2003 at 01:15:48PM -0400, Harold L Hunt II wrote: >Don't send these messages to the Cygwin maiiling list. That will only >lead to them ignoring you if you later have a legitimate question. Hmm. AFAICT, this discussion does belong in both groups until we narrow down what is causing the crash. >You say you are getting a "Signal 11" error message, but I don't see a >reference to which program is actually crashing. Previous email mentions that the program in question is xdvi. It even received confirmation, right here in cygwin-xfree. However neither of the previous messages nor this message are going to help much since there is no accompanying information about the environment in which the crashes occur. This is why the standard response is to direct people to the problems page where attaching cygcheck output is suggested. Attaching cygcheck output is something that Fergus has seemed reluctant to do. The cygwin problems page also has a lot of tips for reporting problems, one of which is to not send email with vague subjects. I have already requested that the xdvi package maintainer jump into this discussion so maybe they will have some insight. cgf -- 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/