From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: [22.1.90]: Point before start of properties Date: Tue, 12 Feb 2008 13:32:01 -0500 Message-ID: References: <6EE216E1AA959543A555C60FF34FB76702E48034@maileube01.misys.global.ad> <87wspcj0ou.fsf@stupidchicken.com> <6EE216E1AA959543A555C60FF34FB76702EED4A1@maileube01.misys.global.ad> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1202841139 5559 80.91.229.12 (12 Feb 2008 18:32:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 Feb 2008 18:32:19 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, Chong Yidong To: "Marshall\, Simon" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 12 19:32:41 2008 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 1JOzvs-0004hv-KQ for ged-emacs-devel@m.gmane.org; Tue, 12 Feb 2008 19:32:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JOzvP-0007JH-1i for ged-emacs-devel@m.gmane.org; Tue, 12 Feb 2008 13:32:11 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JOzvL-0007JA-I3 for emacs-devel@gnu.org; Tue, 12 Feb 2008 13:32:07 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JOzvJ-0007Iq-EQ for emacs-devel@gnu.org; Tue, 12 Feb 2008 13:32:06 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JOzvJ-0007In-7c for emacs-devel@gnu.org; Tue, 12 Feb 2008 13:32:05 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JOzvI-0008Bk-UR for emacs-devel@gnu.org; Tue, 12 Feb 2008 13:32:05 -0500 Original-Received: from mail.gnu.org ([199.232.76.166] helo=mx10.gnu.org) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JOzvI-0008Hf-MP for emacs-pretest-bug@gnu.org; Tue, 12 Feb 2008 13:32:04 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JOzvF-0008Ab-IO for emacs-pretest-bug@gnu.org; Tue, 12 Feb 2008 13:32:04 -0500 Original-Received: from vpn-132-204-232-187.acd.umontreal.ca ([132.204.232.187] helo=ceviche.home) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JOzvF-0008AR-78 for emacs-pretest-bug@gnu.org; Tue, 12 Feb 2008 13:32:01 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id 6D504B40DF; Tue, 12 Feb 2008 13:32:01 -0500 (EST) In-Reply-To: <6EE216E1AA959543A555C60FF34FB76702EED4A1@maileube01.misys.global.ad> (Simon Marshall's message of "Tue, 12 Feb 2008 17:52:19 -0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:88895 gmane.emacs.pretest.bugs:21053 Archived-At: > I can reproduce it (ie, it breaks on the call to error as above) with > lucid and motif scrollbars (tried with gcc-4.1.2) > I can reproduce it with gcc-4.1.2 (-g and -g -O2) and gcc-4.2.3 (-g -O > and -g -O2). > I cannot reproduce it with gcc-4.2.3 (-g) and CC-5.7 (-g). So, adding -O (or -O2) to gcc-4.2.3 triggers the problem, and switching to gcc-4.1.2 triggers it as well? It does sound like it may be a compiler bug, but [putting on my compiler writer hat] it's still at least as likely that the bug is in our code and just isn't triggered in more common circumstances (e.g. a missing `volatile' or something like that, maybe?). First thing: try to reproduce the problem with -DENABLE_CHECKING. This may help us catch the problem at some earlier poin in the execution (it's a long shot, but you never know). Then try to narrow down the problematic source file: compile all files with "gcc-4.2.3 -g" except for one (e.g. intervals.c) and see if you con still reproduce the problem. If you can, recompile intervals.c with "gcc-4.2.3 -g" to double check that the problem then disappears. If that's not that file, then use binary search to figure out which file is causing trouble. Stefan