From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: emacs-21.1.94 crash in gnus on Windows Date: Tue, 16 Mar 2010 20:42:02 +0000 Message-ID: <84eijkm21x.fsf@gmail.com> References: <84634x887o.fsf@gmail.com> <4B9F7F5F.1040504@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1268772154 22597 80.91.229.12 (16 Mar 2010 20:42:34 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 16 Mar 2010 20:42:34 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 16 21:42:29 2010 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.69) (envelope-from ) id 1Nrdau-0007oS-SR for ged-emacs-devel@m.gmane.org; Tue, 16 Mar 2010 21:42:29 +0100 Original-Received: from localhost ([127.0.0.1]:42210 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nrdau-0004rI-4Y for ged-emacs-devel@m.gmane.org; Tue, 16 Mar 2010 16:42:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nrdan-0004o9-MT for emacs-devel@gnu.org; Tue, 16 Mar 2010 16:42:21 -0400 Original-Received: from [140.186.70.92] (port=49364 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nrdam-0004ks-4y for emacs-devel@gnu.org; Tue, 16 Mar 2010 16:42:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nrdak-00049B-6c for emacs-devel@gnu.org; Tue, 16 Mar 2010 16:42:20 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:42877) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nrdaj-000495-SL for emacs-devel@gnu.org; Tue, 16 Mar 2010 16:42:18 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Nrdai-0007ka-Er for emacs-devel@gnu.org; Tue, 16 Mar 2010 21:42:16 +0100 Original-Received: from bb-87-81-240-236.ukonline.co.uk ([87.81.240.236]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Mar 2010 21:42:16 +0100 Original-Received: from andrewjmoreton by bb-87-81-240-236.ukonline.co.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Mar 2010 21:42:16 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 37 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: bb-87-81-240-236.ukonline.co.uk User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.94 (windows-nt) Cancel-Lock: sha1:NEO+I7kJYrRwtk6F1f/pY19742E= X-Antivirus: avast! (VPS 100316-0, 16/03/2010), Outbound message X-Antivirus-Status: Clean X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:122072 Archived-At: On Tue 16 Mar 2010, Eli Zaretskii wrote: >> Date: Tue, 16 Mar 2010 12:53:51 +0000 >> From: Andy Moreton >> CC: emacs-devel@gnu.org >> >> > First, please file a bug report with this information. >> >> I've sent a bug report (from another machine after recreating the crash). > > Didn't see it yet. So I'm responding here, for the time being. Details at http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5730 >> emacs was configured on both machines with "--no-opt". I've added details of >> the crash in the bug report below. >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x01030355 in pos_visible_p (w=0x307c800, charpos=0x5ad, x=0x82f0c4, >> y=0x82f0c0, rtop=0x82f0d8, >> rbot=0x82f0d4, rowh=0x82f0d0, vpos=0x82f0cc) at xdisp.c:1396 >> 1396 for (; glyph < end > > Hmm, that's a strange place to get hit by SIGSEGV. Can you try to see > what exactly caused the crash? When in doubt, I usually disassemble > the vicinity of the address where it crashed (0x01030355 in this > case), find the instruction that crashed, and then compare the > disassembly to the source to find which source line the failed > instruction came from. The GDB command "info line" might help in the > initial estimation of the source line to which the failed address > belongs. I'll try to reproduce it and report back if I can shed any further light. I haven't supplied any command line arguments when running under gdb - do I need to use "-Q" to get something you can reproduce ? AndyM