From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Ok, here is the bug I have been looking for. Kim, not Jan... Date: Wed, 02 Mar 2005 00:52:13 +0100 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1109722667 29230 80.91.229.2 (2 Mar 2005 00:17:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 2 Mar 2005 00:17:47 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 02 01:17:47 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D6HYT-00067k-KX for ged-emacs-devel@m.gmane.org; Wed, 02 Mar 2005 01:17:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6Hr8-000686-4X for ged-emacs-devel@m.gmane.org; Tue, 01 Mar 2005 19:36:50 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D6Hqi-00062y-4u for emacs-devel@gnu.org; Tue, 01 Mar 2005 19:36:24 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D6Hqh-00061J-EM for emacs-devel@gnu.org; Tue, 01 Mar 2005 19:36:23 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6Hg5-0001tD-59 for emacs-devel@gnu.org; Tue, 01 Mar 2005 19:25:25 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D6H9z-0007T2-2Z for emacs-devel@gnu.org; Tue, 01 Mar 2005 18:52:15 -0500 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1D6H9y-00060H-Mg; Tue, 01 Mar 2005 18:52:14 -0500 Original-To: storm@cua.dk (Kim F. Storm) In-Reply-To: (Kim F. Storm's message of "Wed, 02 Mar 2005 00:24:11 +0100") 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:34019 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34019 storm@cua.dk (Kim F. Storm) writes: > storm@cua.dk (Kim F. Storm) writes: > >> David Kastrup writes: >> >>> With -fno-crossjumping, the real assert came to light. >>> >>> It is xdisp.c in line 6122: > > In my checkout, the xassert is in line 12290. Talk about me being imprecise... probably confused this with another buffer. > I have now eliminated that xassert. Well, I have now eliminated all xasserts on my computer for now, and I find it highly embarrassing that I have to tell people that want to test drive Emacs without becoming a debugger-savvy developer that they have to patch around in the source to get it to workable state. I have spent about a week for a total of 4 of them (the last being very elusive, partly due to my stupidity) that basically were of the "well, if we get a test case where Emacs does not scroll in the right direction, it may also possibly trigger the assert, and this is something that we may or may not do something about before the release" category. It has been a very unproductive waste of time for me. It would be one thing if I could see that it does in any manner improve our chance of getting _valuable_ feedback (instead of "it crashed, and even had I been running it in a debugger, the screen would no longer be updated to show what I had been doing" kind of reports). -- David Kastrup, Kriemhildstr. 15, 44793 Bochum