From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: How to debug out of memory situation? Date: Wed, 28 May 2003 19:57:58 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <84n0h8l98r.fsf@lucy.is.informatik.uni-duisburg.de> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1054166809 30187 80.91.224.249 (29 May 2003 00:06:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 29 May 2003 00:06:49 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu May 29 02:06:48 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19LAwS-0007qk-00 for ; Thu, 29 May 2003 02:06:48 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19LBAr-0005Dz-00 for ; Thu, 29 May 2003 02:21:41 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19LAxH-0006CK-7T for emacs-devel@quimby.gnus.org; Wed, 28 May 2003 20:07:39 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19LAvN-0005q7-4p for emacs-devel@gnu.org; Wed, 28 May 2003 20:05:41 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19LAps-0004J4-8L for emacs-devel@gnu.org; Wed, 28 May 2003 20:00:01 -0400 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19LAnu-0002ur-F6 for emacs-devel@gnu.org; Wed, 28 May 2003 19:57:58 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.20) id 19LAnu-0001FC-7s; Wed, 28 May 2003 19:57:58 -0400 Original-To: kai.grossjohann@gmx.net (=?iso-8859-1?q?Kai_Gro=DFjohann?=) In-reply-to: <84n0h8l98r.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@gmx.net) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:14395 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:14395 If you put a breakpoint in memory_full, you will be able to make a backtrace. If Emacs is continuing to use memory for a certain purpose and ran out while trying to do more of that, you should see within a few cases what the pattern is. It might be useful to add more history records of why memory was allocated, for the last 20 times (say). It is not easy to see how to record the history. A useful history record might really want to be a backtrace of some sort. Perhaps a list of the innermost 10 Lisp functions (which can be found by scanning `backlist') would be useful.