From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: backtrace sets print-level to 3 Date: Thu, 30 Sep 2010 13:15:46 +0200 Message-ID: <83fwwrpjml.fsf@gnu.org> References: <83k4m3pozl.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1285845406 30425 80.91.229.12 (30 Sep 2010 11:16:46 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 30 Sep 2010 11:16:46 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 30 13:16:44 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P1H80-0001JB-6e for ged-emacs-devel@m.gmane.org; Thu, 30 Sep 2010 13:16:44 +0200 Original-Received: from localhost ([127.0.0.1]:40201 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1H7y-0003jn-Vq for ged-emacs-devel@m.gmane.org; Thu, 30 Sep 2010 07:16:43 -0400 Original-Received: from [140.186.70.92] (port=49288 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1H7n-0003i1-UD for emacs-devel@gnu.org; Thu, 30 Sep 2010 07:16:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1P1H7j-0007DO-BR for emacs-devel@gnu.org; Thu, 30 Sep 2010 07:16:31 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:39577) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P1H7j-0007DH-0s for emacs-devel@gnu.org; Thu, 30 Sep 2010 07:16:27 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0L9K00B004KNB100@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Thu, 30 Sep 2010 13:15:43 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([77.126.123.60]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L9K00BS14M61D70@a-mtaout20.012.net.il>; Thu, 30 Sep 2010 13:15:43 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:131101 Archived-At: > X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD > autolearn=unavailable version=3.3.1 > From: Lars Magne Ingebrigtsen > Date: Thu, 30 Sep 2010 11:42:44 +0200 > > Eli Zaretskii writes: > > > Can you show an example of this limitation in action? I don't recall > > having any problems with Lisp backtraces, they are certainly longer > > than 3 levels. Maybe I'm missing something. > > The following backtrace was posted on the Gnus mailing list, and all > those dots seem to indicate.... something... I assumed print-level, > since print-length was nil: > > nnimap-insert-partial-structure((("text" "plain" ("charset" "iso-8859-1") NIL NIL "quoted-printable" 57 2 NIL "1" NIL NIL) ("message" "rfc822" NIL NIL NIL "7bit" 16383 ("Tue, 28 Sep 2010 07:40:57 -0700 (PDT)" "LinkedIn Network Updates, 9/28/2010" ... ... ... ... NIL NIL NIL "<213149815.58720010.1285684857650.JavaMail.app@ech3-cdn43.prod>") (... ... "alternative" ... NIL NIL NIL) "2" NIL ("inline" NIL) NIL NIL) "mixed" ("boundary" "=-=-=") NIL NIL NIL) (("1" "Her er problemartikkelen jeg nevnte p=E5 gnus-gruppa:\n\n"))) What about eval-expression-print-length? Could it be that it's the one that causes the ellipsis? Anyway, I just did a little experiment in today's bzr: emacs -Q Type (frame-parameter 'foo) Go to the right paren and type C-j and got this backtrace: Debugger entered--Lisp error: (wrong-number-of-arguments frame-parameter 1) (frame-parameter (quote foo)) eval((frame-parameter (quote foo))) eval-last-sexp-1(t) eval-last-sexp(t) eval-print-last-sexp() call-interactively(eval-print-last-sexp nil nil) This is more than 3 levels, and actually is a full backtrace, right upto call-interactively. So it looks like there's no stack depth limitation at work here.