From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Brian Dessent Newsgroups: gmane.os.cygwin,gmane.emacs.devel Subject: Re: stackdump on cygwin (was: is there a cygwin maintainer for gnu emacs?) Date: Tue, 16 Aug 2005 02:05:11 -0700 Message-ID: <4301AC47.650027FA@dessent.net> References: Reply-To: cygwin@cygwin.com NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1124183023 5649 80.91.229.2 (16 Aug 2005 09:03:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 16 Aug 2005 09:03:43 +0000 (UTC) Cc: jbuehler@spirentcom.com, emacs-devel@gnu.org Original-X-From: cygwin-return-111869-goc-cygwin=m.gmane.org@cygwin.com Tue Aug 16 11:03:41 2005 Return-path: Original-Received: from sourceware.org ([12.107.209.250]) by ciao.gmane.org with smtp (Exim 4.43) id 1E4xLG-0002OQ-1C for goc-cygwin@gmane.org; Tue, 16 Aug 2005 11:02:42 +0200 Original-Received: (qmail 14467 invoked by alias); 16 Aug 2005 09:02:34 -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 14413 invoked by uid 22791); 16 Aug 2005 09:02:30 -0000 Original-Received: from dessent.net (HELO dessent.net) (69.60.119.225) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 16 Aug 2005 09:02:30 +0000 Original-Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.52) id 1E4xL2-00062Z-8W; Tue, 16 Aug 2005 09:02:28 +0000 Original-To: emacs user , cygwin@cygwin.com X-IsSubscribed: yes Xref: news.gmane.org gmane.os.cygwin:68105 gmane.emacs.devel:42107 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:42107 emacs user wrote: > here is a sample emacs.exe.stackdump file I get when emacs crashes. in the > absence of a detailed gdb GC debugging which I dont know how to do, does > this help? I don't know anything about emacs, but I don't think this will help anyone find the problem. A stack trace without symbols (i.e. just numbers) contains no useable information. And since it appears that you are running a self-compiled version (in /usr/local) then it is even more useless since your offsets are going to be unique. It would be better for you to set the error_start parameter of the CYGWIN environment variable so that gdb is launched on the fault, and get a stack backtrace. Though this will suffer from the same problem unless you've compiled from source with debugging information enabled. A backtrace with symbolic function names and/or line numbers is really the only useful form. Brian