From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Fix stack overflow in notmuch-wash-tidy-citations
In-Reply-To: <87eif2tja1.fsf@gmail.com>
References: <1279279955-3110-1-git-send-email-sojkam1@fel.cvut.cz>
	<87eif2tja1.fsf@gmail.com>
User-Agent: Notmuch/0.3.1-80-g86b7c46 (http://notmuchmail.org) Emacs/23.2.1
	(x86_64-pc-linux-gnu)
Date: Sun, 18 Jul 2010 17:00:22 +0200
Message-ID: <87pqykomwp.fsf@steelpick.2x.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: list

Hi Dmitry,

On Sat, 17 Jul 2010, Dmitry Kurochkin wrote:
> I have 2 messages that cause emacs segfault.

My patch didn't fix a segfault but stack overflow which was reported by
emacs in its *Messages* buffer without crashing.

> Both are notifications from svn. One is 37933 lines, 1,2M. Another is
> huge - 963179 lines, 31M. I believe the root cause is the same for
> both segfaults.
> 
> Your patch does not fix the problem, unfortunately. Can you advise how
> to debug this segfault? Build emacs with debug symbols and get backtrace
> from gdb?

I'm more Emacs user then developer so I cannot give you much detailed
information. First, try to check
http://mid.gmane.org/87pr0t5h1q.fsf@yoom.home.cworth.org and Emacs
bug#6214. There may by a fix your problem.


> Debug notmuch lisp code (how?)? Enable some verbose logging in emacs?

To debug elisp code I open the source in Emacs, move the point to the
function I'm interested in and press C-u C-M-x. This instruments the
function code so that the next time the function is invoked, elisp
debugger appears and you can execute the function step by step and
inspect variables.

Maybe, some Emacs guru can give you a better advice.

Bye
Michal