From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs (HEAD) crash on M$ (XP) built with MinGW Date: Tue, 21 Oct 2008 10:30:43 +0200 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1224578216 20376 80.91.229.12 (21 Oct 2008 08:36:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 21 Oct 2008 08:36:56 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org To: dhruva Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 21 10:37:54 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KsCkT-0004Sy-4W for ged-emacs-devel@m.gmane.org; Tue, 21 Oct 2008 10:37:53 +0200 Original-Received: from localhost ([127.0.0.1]:43708 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsCjN-0006fB-QQ for ged-emacs-devel@m.gmane.org; Tue, 21 Oct 2008 04:36:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KsCev-0003hl-FP for emacs-devel@gnu.org; Tue, 21 Oct 2008 04:32:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KsCet-0003gC-Jw for emacs-devel@gnu.org; Tue, 21 Oct 2008 04:32:08 -0400 Original-Received: from [199.232.76.173] (port=41097 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsCes-0003fu-Ns for emacs-devel@gnu.org; Tue, 21 Oct 2008 04:32:06 -0400 Original-Received: from mtaout4.012.net.il ([84.95.2.10]:46254) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KsCes-0007ug-Mg for emacs-devel@gnu.org; Tue, 21 Oct 2008 04:32:07 -0400 Original-Received: from HOME-C4E4A596F7 ([77.126.98.197]) by i_mtaout4.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K92005AGYDIJ0F0@i_mtaout4.012.net.il> for emacs-devel@gnu.org; Tue, 21 Oct 2008 10:32:11 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 9.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:104735 Archived-At: > Date: Tue, 21 Oct 2008 13:25:38 +0530 > From: dhruva > Cc: "Eli Zaretskii" , emacs-devel@gnu.org > > > FWIW, I cannot reproduce it either. > > > >> If the fix is safe (defensive), IMHO we could get that in as I > >> continue to debug by adding some extra code in the 'if' block. > > > > IMO is best to let it stand, or even add an assertion; the best way to > > catch it is by having it happen. I completely agree with Juanma: your ``defensive'' fix will simply sweep the problem under the carpet, and it won't get fixed for a long time, considering that no one can currently reproduce it except yourself. > Could we just log the required extra information for further debugging > when that happens? Allowing it to crash is a serious inconvenience > (especially for me since I use the code from HEAD for my regular > work) Then please help us debug and fix this ASAP. TIA