From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: Recent enabling of xassert Date: Thu, 10 Feb 2005 12:15:44 +0100 Message-ID: References: <420B34F9.7060109@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1108035533 31696 80.91.229.2 (10 Feb 2005 11:38:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 10 Feb 2005 11:38:53 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 10 12:38:53 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1CzCel-0000fE-V6 for ged-emacs-devel@m.gmane.org; Thu, 10 Feb 2005 12:38:48 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CzCtU-0000aY-Gx for ged-emacs-devel@m.gmane.org; Thu, 10 Feb 2005 06:54:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CzCcw-0005BY-LQ for emacs-devel@gnu.org; Thu, 10 Feb 2005 06:36:55 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CzCct-00058t-Mb for emacs-devel@gnu.org; Thu, 10 Feb 2005 06:36:53 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CzCcs-00056X-HM for emacs-devel@gnu.org; Thu, 10 Feb 2005 06:36:50 -0500 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.34) id 1CzCIR-00055r-S5 for emacs-devel@gnu.org; Thu, 10 Feb 2005 06:15:44 -0500 Original-Received: (qmail 96410 invoked from network); 10 Feb 2005 11:15:40 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 10 Feb 2005 11:15:40 -0000 Original-To: Jason Rumney In-Reply-To: <420B34F9.7060109@gnu.org> (Jason Rumney's message of "Thu, 10 Feb 2005 10:18:33 +0000") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33189 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33189 Jason Rumney writes: > Kim F. Storm wrote: > >>Miles recently enabled xassert unconditionally to catch undiscovered >>bugs in redisplay and other places... >> >>We have now seen several crashes caused by this change -- but none of >>them has been fully diagnosed yet, as this is very hard without having >>easy ways to reproduce the crashes. >> >>Debugging those crashes requires time which I don't have -- so unless >>someone else steps in to help, I suggest we disable xassert again. >> >> > I disagree. xassert should only be disabled for releases. We want to > find the bugs now, even if it takes time to fix them. CVS should not > be considered a stable release. I agree, but... Proving the presense of bugs is no aim in itself (I'm sure there are many bugs, but if they are "mostly harmless" it is not critical to find them). Why detect bugs if we don't have time to fix them (or diagnose them as false xasserts)? Actually, my suggestion was mostly rethorical -- asking/provoking people to help debugging these (potentiall very hard to diagnose) bugs as they are reported. So who can and will help? -- Kim F. Storm http://www.cua.dk