From xemacs-m  Wed Mar 26 04:08:54 1997
Received: from mailbox2.ucsd.edu (mailbox2.ucsd.edu [132.239.1.54])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id EAA24762
	for <xemacs-beta@xemacs.org>; Wed, 26 Mar 1997 04:08:53 -0600 (CST)
Received: from sdnp5.ucsd.edu (sdnp5.ucsd.edu [132.239.79.10]) by mailbox2.ucsd.edu (8.8.5/8.6.9) with SMTP id CAA00713 for <xemacs-beta@xemacs.org>; Wed, 26 Mar 1997 02:08:54 -0800 (PST)
Received: by sdnp5.ucsd.edu (SMI-8.6/SMI-SVR4)
	id CAA18255; Wed, 26 Mar 1997 02:10:45 -0800
Sender: dmoore@sdnp5.ucsd.edu
To: xemacs-beta@xemacs.org
Subject: Re: j-shell and efs don't get along
References: <199703241918.LAA08226@palrel3.hp.com> <y9lg1xk789w.fsf@modas.informatik.uni-tuebingen.de> <fawd8snn7uo.fsf@rlab24.rsn.hp.com> <y9ln2rrg4bn.fsf@modas.informatik.uni-tuebingen.de> <fawn2rrllk0.fsf@rlab24.rsn.hp.com> <y9l4tdzf155.fsf@modas.informatik.uni-tuebingen.de>
X-Face: "oX;zS#-JU$-,WKSzG.1gGE]x^cIg!hW.dq>.f6pzS^A+(k!T|M:}5{_%>Io<>L&{hO7W4cicOQ|>/lZ1G(m%7iaCf,6Qgk0%%Bz7b2-W3jd0m_UG\Y;?]}4s0O-U)uox>P3JN)9cm]O\@,vy2e{`3pb!"pqmRy3peB90*2L
Mail-Copies-To: never
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: David Moore <dmoore@ucsd.edu>
Date: 26 Mar 1997 02:10:44 -0800
In-Reply-To: sperber@informatik.uni-tuebingen.de's message of 26 Mar 1997 10:33:42 +0100
Message-ID: <rvlo7bm09n.fsf@sdnp5.ucsd.edu>
Lines: 35
X-Mailer: Gnus v5.4.37/XEmacs 19.15

sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:

> Shane> This will result in
> Shane>   Lisp nesting exceeds `max-lisp-eval-depth'

> still yields nil, i.e. the EFS handler never got called.  There's some
> evil interaction between default-directory and
> file-name-handlers-alist that needs to be tracked down.  I just spent
> an hour on this, but no dice so far.  (Anybody know how to at least
> get a backtrace out of this situation?)

(setq debug-on-signal t)

If debug-on-error isn't working, then something has slapped a
condition-case in there.  debug-on-signal will work even in
condition-case.

Or (for me) before you start XEmacs in your shell window use `limit' to
make sure that your stacksize limit is something smallish (say 2k).  And
then go in XEmacs, set max-lisp-eval-depth very large (like 5000).  Then
send a C stack trace of the resulting core dump.

Or I guess you could start it in gdb and set a breakpoint on Fsignal and
get the stack trace that way. :)


There could very well be a bug with the filehandler code with
default-directory.  I fixed a garbage collection bug related to some of
this today.

-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | In a cloud bones of steel.

