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 09:12:39 +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 1224560724 3506 80.91.229.12 (21 Oct 2008 03:45:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 21 Oct 2008 03:45:24 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Eli Zaretskii" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 21 05:46:24 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 1Ks8CN-0001Sr-Rf for ged-emacs-devel@m.gmane.org; Tue, 21 Oct 2008 05:46:24 +0200 Original-Received: from localhost ([127.0.0.1]:59925 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ks8BI-0004BD-J0 for ged-emacs-devel@m.gmane.org; Mon, 20 Oct 2008 23:45:16 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ks88t-0002tR-2W for emacs-devel@gnu.org; Mon, 20 Oct 2008 23:42:47 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ks88p-0002s4-Bk for emacs-devel@gnu.org; Mon, 20 Oct 2008 23:42:46 -0400 Original-Received: from [199.232.76.173] (port=51710 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ks88p-0002s0-36 for emacs-devel@gnu.org; Mon, 20 Oct 2008 23:42:43 -0400 Original-Received: from ti-out-0910.google.com ([209.85.142.186]:14097) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ks88n-0003Fu-NH for emacs-devel@gnu.org; Mon, 20 Oct 2008 23:42:42 -0400 Original-Received: by ti-out-0910.google.com with SMTP id u5so1046726tia.10 for ; Mon, 20 Oct 2008 20:42: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=vMLWIBoj6+2oRxxQJ9H385w6qUfNYL1ry7YADL7xK5M=; b=F0ZbnyKyt84IiPo1v15MALS2ICvkN7dZMj+XkUxvNMw0yyLjnxzU+RDLb7uNob6wCn 0m4qbZs49/AfyOoTlyPdIgQPfMm6rHdxv7sM8TrT6pHzYi9FB08QOKrxxmLLx6jvw3g/ zSFQRH/Ek1q5HCS0d4ixSEfKHRoPbvSl1frpQ= 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=TMAuAXLprH0qFiScb+bvD64DXcKvoLnJIxVzRUi5MhRrZhckFDu+v2ttJYqHxLkdtR +RYGn5sM+L1AQRPHaF+6xfDW7MPRjT2KmYa+YJUcBGr428Wf/A7rHbC4OrC0YA0cabOD 1X9QqKwA05940kBnIvFw2fd9O2J4vpbO3I728= Original-Received: by 10.110.37.17 with SMTP id k17mr3919164tik.6.1224560559734; Mon, 20 Oct 2008 20:42:39 -0700 (PDT) Original-Received: by 10.110.93.2 with HTTP; Mon, 20 Oct 2008 20:42:39 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:104712 Archived-At: Hello, On Mon, Oct 20, 2008 at 8:11 PM, Eli Zaretskii wrote: >> Date: Mon, 20 Oct 2008 18:08:15 +0530 >> From: dhruva >> >> I am still seeing the elusive and infrequent crash. I open a 'C' >> file, maximize the frame and use the page down to scroll down or down >> arrow. I keep hitting this crash off and now. The tried getting 'xbt' >> and could not. > > xbacktrace will not give you any useful information when the crash is > inside redisplay, at least not normally, because redisplay is not > normally triggered by Lisp code. Redisplay is what Emacs normally > does when it is idle (on the C level). > >> (gdb) bt >> #0 0x0103ca47 in next_element_from_string (it=0x82e1ac) at xdisp.c:6263 >> #1 0x0103b03e in get_next_display_element (it=0x82e1ac) at xdisp.c:5655 >> #2 0x0103591d in init_from_display_pos (it=0x82e1ac, w=0x38f0e00, >> pos=0x3af23e0) at xdisp.c:3035 > > Is this optimized build or unoptimized one? If the former, please try built with '--no-opt' (disabled optimization) > If your xdisp.c is current, and assuming that this is an unoptimized > build (and so the backtrace is trustworthy), the problem seems to be > with trying to display something based on some string, which is stored > at it->string. Could you please see what string is that, and what is > its contents? That might give us a clue about whodunit. Sure, I will look at those more closely. It happens when I open a 'C' file with global-font-lock enabled. I will try to get stack dumps with all extra information. -dhruva -- Contents reflect my personal views only!