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: Sun, 15 Jun 2003 11:59:49 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <84n0h8l98r.fsf@lucy.is.informatik.uni-duisburg.de> <84y90bmah0.fsf@lucy.is.informatik.uni-duisburg.de> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1055693141 23254 80.91.224.249 (15 Jun 2003 16:05:41 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 15 Jun 2003 16:05:41 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Jun 15 18:05:36 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 19Ra0e-00062e-00 for ; Sun, 15 Jun 2003 18:05:36 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19RaNe-0006SZ-00 for ; Sun, 15 Jun 2003 18:29:22 +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 19Ra33-0002EU-Os for emacs-devel@quimby.gnus.org; Sun, 15 Jun 2003 12:08:05 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19Ra19-0001Tn-PH for emacs-devel@gnu.org; Sun, 15 Jun 2003 12:06:07 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19RZvJ-0000Gq-5R for emacs-devel@gnu.org; Sun, 15 Jun 2003 12:00:08 -0400 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19RZv3-0008Og-MK for emacs-devel@gnu.org; Sun, 15 Jun 2003 11:59:49 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.20) id 19RZv3-0003VJ-DG; Sun, 15 Jun 2003 11:59:49 -0400 Original-To: kai.grossjohann@gmx.net (=?iso-8859-1?q?Kai_Gro=DFjohann?=) In-reply-to: <84y90bmah0.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:15105 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:15105 Once you get a memory-full error in a certain session, you probably won't learn anything more from successive memory-full errors in the same session. They are all secondary consequences of the first. However, if you look at the first memory-full error in each session, for a number of sessions, they may show a pattern that indicates something about what code is causing the problem. The first instance, as you reported it, is this: "gnus-get-newsgroup-headers-xover" "gnus-agent-fetch-group-1" "gnus-agent-fetch-session" "call-interactively"