From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.help Subject: RE: max-lisp-eval-depth Date: Wed, 30 Jan 2013 13:27:42 -0800 Message-ID: <2648A59CF1C84AF884198413B12B188D@us.oracle.com> References: <1359574923315-276835.post@n5.nabble.com> <6DCBB657-5C42-4655-A9E4-AFCF4CC3853B@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1359581275 1747 80.91.229.3 (30 Jan 2013 21:27:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 30 Jan 2013 21:27:55 +0000 (UTC) Cc: Help-gnu-emacs@gnu.org To: "'Perry Smith'" , "'drain'" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Jan 30 22:28:15 2013 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1U0fCY-0003lO-Pi for geh-help-gnu-emacs@m.gmane.org; Wed, 30 Jan 2013 22:28:14 +0100 Original-Received: from localhost ([::1]:36903 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U0fCG-0002Zh-6k for geh-help-gnu-emacs@m.gmane.org; Wed, 30 Jan 2013 16:27:56 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:43509) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U0fCA-0002ZW-P5 for Help-gnu-emacs@gnu.org; Wed, 30 Jan 2013 16:27:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U0fC9-0002Jl-OT for Help-gnu-emacs@gnu.org; Wed, 30 Jan 2013 16:27:50 -0500 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:42521) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U0fC9-0002JA-Gr for Help-gnu-emacs@gnu.org; Wed, 30 Jan 2013 16:27:49 -0500 Original-Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r0ULRiaH018058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Jan 2013 21:27:47 GMT Original-Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r0ULRhLM009291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Jan 2013 21:27:44 GMT Original-Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r0ULRhBc001018; Wed, 30 Jan 2013 15:27:44 -0600 Original-Received: from dradamslap1 (/130.35.178.8) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 30 Jan 2013 13:27:43 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <6DCBB657-5C42-4655-A9E4-AFCF4CC3853B@gmail.com> Thread-Index: Ac3/JHDMwgr690r5Tf2NijHzhVYU8QAC8jEw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 141.146.126.69 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:88875 Archived-At: > Mine is set to 600 (emacs 24.2) on two different platforms. > > Would setting debug-on-error to t help? Then you would see > the stack and that might give you a hint. It may be some > data structure is looped back on itself and its not suppose > to be causing infinite recursion. The error that max-lisp-eval-depth is exceeded is nearly always an infinite-recursion problem. Bisect your init file to try to identify the culprit code. You might need to recompile that code or load it without compiling it. Or perhaps (most likely) it is just buggy and needs to be fixed. But the point is to respond to a max-lisp-eval-depth error by looking for a code problem, not by increasing that variable value.