From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.os.cygwin,gmane.emacs.devel Subject: Re: is there a cygwin maintainer for gnu emacs? Date: Thu, 11 Aug 2005 06:37:25 +0300 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1123731505 5504 80.91.229.2 (11 Aug 2005 03:38:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 11 Aug 2005 03:38:25 +0000 (UTC) Cc: jbuehler@spirentcom.com, cygwin@cygwin.com, emacs-devel@gnu.org Original-X-From: cygwin-return-111588-goc-cygwin=m.gmane.org@cygwin.com Thu Aug 11 05:38:22 2005 Return-path: Original-Received: from sourceware.org ([12.107.209.250]) by ciao.gmane.org with smtp (Exim 4.43) id 1E33tD-0006r2-I2 for goc-cygwin@gmane.org; Thu, 11 Aug 2005 05:37:55 +0200 Original-Received: (qmail 29406 invoked by alias); 11 Aug 2005 03:37:41 -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 29295 invoked by uid 22791); 11 Aug 2005 03:37:33 -0000 Original-Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 11 Aug 2005 03:37:33 +0000 Original-Received: from HOME-C4E4A596F7 (IGLD-84-228-237-108.inter.net.il [84.228.237.108]) by nitzan.inter.net.il (MOS 3.6.5-GR) with ESMTP id BCT83868 (AUTH halo1); Thu, 11 Aug 2005 06:37:23 +0300 (IDT) Original-To: "emacs user" In-reply-to: (emacs_user@hotmail.com) Xref: news.gmane.org gmane.os.cygwin:67824 gmane.emacs.devel:41906 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:41906 > From: "emacs user" > Cc: cygwin@cygwin.com, emacs-devel@gnu.org > Date: Wed, 10 Aug 2005 16:18:20 -0400 > > I guess my question as a fairly naive user is who will bedoing that GC > debugging. Someone who can reproduce the problem. If that's only you, then you will have to do the debugging. > I am happy to check things in gdb following instructions from > one of you experts... Like I said: the instructions are in etc/DEBUG. We can help interpret the results, if you cannot figure them out, but there's no sense for us to repeat what's already in etc/DEBUG before you post some more information using the methodology described there.