From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: unpredictable emacs 21 crashes Date: Sun, 16 Jun 2002 08:43:20 +0300 (IDT) Sender: emacs-devel-admin@gnu.org Message-ID: References: <200206151414.g5FEE0G10343@aztec.santafe.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1024206505 15426 127.0.0.1 (16 Jun 2002 05:48:25 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 16 Jun 2002 05:48:25 +0000 (UTC) Cc: reid+usenet@astro.utoronto.ca, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17JStl-00040h-00 for ; Sun, 16 Jun 2002 07:48:25 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17JTJM-00014P-00 for ; Sun, 16 Jun 2002 08:14:52 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17JStT-0002Qf-00; Sun, 16 Jun 2002 01:48:07 -0400 Original-Received: from is.elta.co.il ([199.203.121.2]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17JSqk-0002On-00; Sun, 16 Jun 2002 01:45:18 -0400 Original-Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id IAA26761; Sun, 16 Jun 2002 08:43:20 +0300 (IDT) X-Sender: eliz@is Original-To: Richard Stallman In-Reply-To: <200206151414.g5FEE0G10343@aztec.santafe.edu> Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:4903 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:4903 On Sat, 15 Jun 2002, Richard Stallman wrote: > Most likely, whatever called GC won't be relevant. > The crash is probably due to invalid data. To analyze it > you need to study the data being worked on in the innermost frames. > By working back one frame at a time, you can see what data structure > the invalid objects are found in. The vector last_marked (see > alloc.c) can help you trace this back. There's some information about debugging these problems in etc/DEBUG.