From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: Re: Emacs 21.2 - Garbage collector frenzy :-) Date: Mon, 22 Apr 2002 10:23:46 +0300 (IDT) Sender: bug-gnu-emacs-admin@gnu.org Message-ID: References: NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1019456842 19140 127.0.0.1 (22 Apr 2002 06:27:22 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 22 Apr 2002 06:27:22 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16zXIH-0004yb-00 for ; Mon, 22 Apr 2002 08:27:21 +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 16zXIE-0004mB-00; Mon, 22 Apr 2002 02:27:18 -0400 Original-Received: from is.elta.co.il ([199.203.121.2]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16zXGF-0004WA-00 for ; Mon, 22 Apr 2002 02:25:15 -0400 Original-Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id KAA12292; Mon, 22 Apr 2002 10:23:46 +0300 (IDT) X-Sender: eliz@is Original-To: =?iso-8859-1?q?Fran=E7ois?= Pinard In-Reply-To: Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:857 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:857 On 21 Apr 2002, =?iso-8859-1?q?Fran=E7ois?= Pinard wrote: > This is with Emacs 21.2 that I thought about checking if the problem is > related to garbage collection, but I remember having observed such CPU > loops in the latest pretest before 21.2, without much to say about them at > the time. Not that I have so much more to say now... How could I proceed > towards better reporting the problem? Try this: - Run Emacs under GDB. Be sure to start GDB from the `src' directory of the Emacs source tree, to make it use the .gdbinit file with all the additional commands it defines. - When the problem happens, interrupt Emacs with "kill -TSTP PID", where PID is the Emacs process ID, or by typing "C-c" at the window where Emacs is run under GDB. This should cause GDB to kick in. - At the GDB prompt, type "xbacktrace". It should produce the Lisp-level backtrace showing what function caused the massive GC. - Still at the GDB prompt, type "bt" for the C-level backtrace. - Repeat the above 3 steps several times, each time continuing Emacs after producing the backtraces. After that, you should have enough information to figure out what feature(s) causes the massive GC. Post that info here. The file etc/DEBUG in the Emacs distribution has more hints for debugging Emacs.