From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Variable binding depth exceeds max-specpdl-size
Date: Mon, 05 Jul 2004 18:29:10 -0400 [thread overview]
Message-ID: <usmc6dr61.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <87wu1is4jl.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
> Platform: Intel Pentium M,
> debian sarge (testing/unstable),
> xemacs21 21.4.15-1,
> No Gnus v0.3 (today's CVS)
>
> When entering an agentized nnimap group against the Exchange server at
> work, in offline mode at home, I get the message "Variable binding
> depth exceeds max-specpdl-size" when I first try to enter the group.
> When I try to enter the group again, I still get the message, but I am
> able to enter the group. I also get the message when trying to exit
> the summary with `q' after changing the state of the group (ie. read
> or reply to messages).
>
> The stack trace for the message is:
>
> Signaling: (error "Variable binding depth exceeds max-specpdl-size")
> gnus-get-function((nnimap "somecompany" (nnimap-address "somemachine.somecompany.com")) request-type)
> nnagent-request-type("INBOX" nil)
> nnagent-request-type("INBOX" nil)
> nnagent-request-type("INBOX" nil)
> nnagent-request-type("INBOX" nil)
> nnagent-request-type("INBOX" nil)
...
> nnagent-request-type("INBOX" nil)
> nnagent-request-type("INBOX" nil)
> nnagent-request-type("INBOX" nil)
> gnus-request-type("nnimap+somecompany:INBOX")
> gnus-news-group-p("nnimap+somecompany:INBOX")
> gnus-xmas-setup-summary-toolbar()
> run-hooks(gnus-xmas-setup-summary-toolbar)
> apply(run-hooks gnus-xmas-setup-summary-toolbar)
> gnus-run-hooks(gnus-summary-mode-hook)
> gnus-summary-mode("nnimap+somecompany:INBOX")
> gnus-summary-setup-buffer("nnimap+somecompany:INBOX")
> gnus-summary-read-group-1("nnimap+somecompany:INBOX" nil t nil nil nil)
> gnus-summary-read-group("nnimap+somecompany:INBOX" nil t nil nil nil nil)
> gnus-group-read-group(nil t)
> gnus-group-select-group(nil)
> gnus-topic-select-group(nil)
> call-interactively(gnus-topic-select-group)
How are you at debugging lisp? If you do the following, you should be
able to debug gnus to see what is going wrong (It's not
nnagent-request-type itself but an interaction between it,
gnus-online, gnus-get-function, and gnus-agent-get-function).
M-x load-library <ret>gnus<ret>
M-x load-library <ret>gnus-agent.el<ret>
M-x load-library <ret>gnus-int.el<ret>
M-x load-library <ret>gnus.el<ret>
M-x load-library <ret>nnagent.el<ret>
M-x debug-on-entry <ret>nnagent-request-type<ret>
Kevin
next prev parent reply other threads:[~2004-07-05 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 18:16 Steinar Bang
2004-07-05 22:29 ` Kevin Greiner [this message]
2004-07-06 16:16 ` Steinar Bang
2004-07-06 19:42 ` Steinar Bang
2004-07-08 14:47 ` Kevin Greiner
2004-10-01 20:59 ` Steinar Bang
2004-10-01 22:17 ` Steinar Bang
2004-10-01 22:38 ` Steinar Bang
2004-10-01 22:48 ` Steinar Bang
2004-10-02 5:50 ` Kevin Greiner
2004-10-02 6:50 ` Steinar Bang
2012-12-13 8:30 Rémi Letot
2012-12-14 0:08 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=usmc6dr61.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).