From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dhruva Newsgroups: gmane.emacs.devel Subject: Re: Emacs (HEAD) crash on M$ (XP) built with MinGW Date: Tue, 21 Oct 2008 13:25:38 +0530 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1224579073 23460 80.91.229.12 (21 Oct 2008 08:51:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 21 Oct 2008 08:51:13 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: "Juanma Barranquero" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 21 10:52:12 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 1KsCy9-0001zI-Ak for ged-emacs-devel@m.gmane.org; Tue, 21 Oct 2008 10:52:01 +0200 Original-Received: from localhost ([127.0.0.1]:39863 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsCx4-0002A9-3f for ged-emacs-devel@m.gmane.org; Tue, 21 Oct 2008 04:50:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KsCwq-00025D-2p for emacs-devel@gnu.org; Tue, 21 Oct 2008 04:50:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KsCwo-000244-FJ for emacs-devel@gnu.org; Tue, 21 Oct 2008 04:50:39 -0400 Original-Received: from [199.232.76.173] (port=37294 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsCwn-00023T-Jg for emacs-devel@gnu.org; Tue, 21 Oct 2008 04:50:37 -0400 Original-Received: from mx20.gnu.org ([199.232.41.8]:10245) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KsCwn-0002z7-7O for emacs-devel@gnu.org; Tue, 21 Oct 2008 04:50:37 -0400 Original-Received: from ti-out-0910.google.com ([209.85.142.184]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KsC5d-0007S4-Re for emacs-devel@gnu.org; Tue, 21 Oct 2008 03:55:42 -0400 Original-Received: by ti-out-0910.google.com with SMTP id u5so1118532tia.10 for ; Tue, 21 Oct 2008 00:55:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=2wFPU2C6DARXHftTPCqcqr/hUmhc98iZj2vjGkcpTDs=; b=UycuU4cxJs4/+eXTumN8Nzy/VwD9JmB8IEVCFlyOHG9N6/8vUFDW2ewf8UwrO9LyED qnTzfKpP7AXdqxcGtMgR7ywcvfJpQxPnK72RxN1IPuKYI1dq7S9ByTQM/xySpXPFvKec Dv862yK9a2HBj8PkYcruxSL9AMiiF2GrXflrA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=BXKAJXR2P+JszCxO2/4N6qfsgxE3cBfR2UuGD6wJ/m8H800aMxVOaUckoyxUSUPper aF8m4kn39ke2COsD4Bs0ovSuFNXndM/0wjBJwLjsDp+x9E7aBLfHtSictUXrtbtHfRx5 ytdY5yCJrOT5gsUyW2+fwu31t7sia1jVY4yFA= Original-Received: by 10.110.16.9 with SMTP id 9mr5688865tip.53.1224575738936; Tue, 21 Oct 2008 00:55:38 -0700 (PDT) Original-Received: by 10.110.93.2 with HTTP; Tue, 21 Oct 2008 00:55:38 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-kernel: by mx20.gnu.org: Linux 2.6 (newer, 2) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:104738 Archived-At: Hello, On Tue, Oct 21, 2008 at 1:11 PM, Juanma Barranquero wrote: > On Tue, Oct 21, 2008 at 09:11, dhruva wrote: > >> I use the same button... > > 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. 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) -dhruva -- Contents reflect my personal views only!