From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: John Owens Newsgroups: gmane.emacs.devel Subject: Re: how to debug an emacs hang? Date: Thu, 20 May 2004 15:59:57 -0700 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1085095979 20501 80.91.224.253 (20 May 2004 23:32:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 20 May 2004 23:32:59 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri May 21 01:32:52 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BQx1w-0002Xm-00 for ; Fri, 21 May 2004 01:32:52 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BQx1v-0004Hc-00 for ; Fri, 21 May 2004 01:32:51 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BQwYz-0002os-4z for emacs-devel@quimby.gnus.org; Thu, 20 May 2004 19:02:57 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BQwWk-0002SB-1d for emacs-devel@gnu.org; Thu, 20 May 2004 19:00:38 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BQwWA-0002H0-6F for emacs-devel@gnu.org; Thu, 20 May 2004 19:00:33 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BQwW9-0002GX-J5 for emacs-devel@gnu.org; Thu, 20 May 2004 19:00:01 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BQwW8-0002NF-00 for ; Fri, 21 May 2004 01:00:01 +0200 Original-Received: from weetabix.ece.ucdavis.edu ([169.237.74.64]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 May 2004 01:00:00 +0200 Original-Received: from john_owens by weetabix.ece.ucdavis.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 May 2004 01:00:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 38 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: weetabix.ece.ucdavis.edu User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (windows-nt) Cancel-Lock: sha1:rvBAoD/Q6HmeoB03UJbScB7KqDs= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23803 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23803 John Owens writes: > I've been running the same emacs (the released version of NT emacs > 21.3) for quite some time, but recently it started hanging while I'm > composing a mail message (via vm-mail), and I made it also hang when > editing a HTML file. It hangs for about a minute (to the point where > it doesn't even refresh) and eventually all my text suddenly appears > and it's all back to normal. Hitting C-g does not seem to do anything > while it is hanging. > > I'd like to figure out how/where it's hanging, but I don't know how I > might do so. Suggestions? Thank you all for the kind replies. I am using a precompiled version from Ted Jump ["GNU Emacs 21.3.1 (i386-msvc-nt5.1.2600) of 2003-03-25 on TJUMP20"], clearly a MSVC compile and not a debug one. I've never actually built one myself on Windows (but have on OS X). The hope was that it would be possible to set a variable that would actually catch some signal and give a backtrace, but that does not seem to be available (or such is my understanding from your replies). Also it happens infrequently enough that running a debug build would probably annoy me. :) However, I appreciate the pointer to the etc/DEBUG docs and will give those a try. The codebase has probably progressed enough since 21.3 was released that I'm probably better off just getting a new CVS build and seeing if the problem is still present, and if so, debugging it instead. (I'm running a CVS build on OS X currently.) One difficulty with that approach is that if I'm getting source from CVS it's always a little dicey to make sure I have a stable version, since I might have got new files in the middle of a checkin. Given the maturity of the 21.3.50 tree, maybe it's getting about time to at least mark a set of files as "alpha1", "alpha2", etc. just to make sure they're stable. Thanks again for the replies. JDO