From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: 16587@debbugs.gnu.org
Subject: bug#16587: 24.3.50; max-specpdl-size exceeded + crash with gnus (shr).
Date: Thu, 30 Jan 2014 18:25:52 -0800 [thread overview]
Message-ID: <874n4k28gf.fsf@building.gnus.org> (raw)
In-Reply-To: <87iot2hjmh.fsf@yahoo.fr> (Nicolas Richard's message of "Wed, 29 Jan 2014 16:51:02 +0100")
Nicolas Richard <theonewiththeevillook@yahoo.fr> writes:
> 2. evaluate the following lines (which happen to be in my ~/.emacs) :
> (setq gnus-select-method (quote (nntp "eu.news.astraweb.com")))
> (setq gnus-secondary-select-methods (quote ((nntp "news.gmane.org") (nntp "news.zoo-logique.org"))))
>
> 3. M-x gnus
>
> 4. navigate to Rotem Yaari's initial report for bug #16577 in nntp+news.gmane.org:gmane.emacs.bugs
Note -- you can access bug reports directly if you have debbugs from
ELPA installed:
(require 'gnus-group)
(setq debug-on-error t)
(gnus-read-ephemeral-emacs-bug-group 16577)
> I get the error:
> shr-descend: Variable binding depth exceeds max-specpdl-size
Yeah, it's a very deeply nested semi-HTML message, and shr uses two
stack frames per nested element.
Hm... it looks like it should be possible to replace `shr-generic' with
a macro, which should halve the number of stack frames. I'll try doing
that...
> Now I do M-x toggle-debug-on-error, open another message in gnus, then
> back to Rotem Yaari's, and that's a crash. (btw it also happens if I
> actiavte debug-on-error from the beginning, it has nothing to do with
> reopening the message)
I get that too.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-01-31 2:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 15:51 bug#16587: 24.3.50; max-specpdl-size exceeded + crash with gnus (shr) Nicolas Richard
2014-01-30 1:17 ` Katsumi Yamaoka
2014-01-30 11:56 ` Nicolas Richard
2014-01-31 2:25 ` Lars Ingebrigtsen [this message]
2014-01-31 2:37 ` Lars Ingebrigtsen
2014-01-31 2:46 ` Lars Ingebrigtsen
2014-01-31 14:28 ` Stefan Monnier
2014-01-31 21:21 ` Lars Ingebrigtsen
2014-01-31 15:00 ` Andy Moreton
2014-01-31 14:23 ` Stefan Monnier
2014-01-31 21:08 ` Lars Ingebrigtsen
2014-01-31 21:18 ` Lars Ingebrigtsen
2014-11-13 20:57 ` Lars Magne Ingebrigtsen
2014-11-13 21:13 ` Lars Magne Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874n4k28gf.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=16587@debbugs.gnu.org \
--cc=theonewiththeevillook@yahoo.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).