GNU bug report logs - #41407
28.0.50; infinite loop "Article 53570 has a nil data header" on "Exiting summary buffer and applying spam rules"

Previous Next

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Sam Steingold <sds <at> gnu.org>
Cc: 41407 <at> debbugs.gnu.org
Subject: bug#41407: 28.0.50; infinite loop "Article 53570 has a nil data header" on "Exiting summary buffer and applying spam rules"
Date: Thu, 06 Aug 2020 09:04:28 +0200

Sam Steingold <sds <at> gnu.org> writes:

>> Anyway, this isn't something that Gnus does by default -- do you have
>> any customisations that trigger this behaviour?
>
> What customisations could possibly cause that?

Well, the thing that's bugging out is apparently something in
gnus/spam.el, which isn't used by default...

> At any rate, this was a few months ago and I have not seen it again
> (knocks on wood ;-))

If this happens again, do a

(setq debug-on-message "has a nil data header")

and perhaps the backtrace will give a hint where the bug originates
from.

I've given spam.el a cursory look-over, and trying to follow the bits
that call the function that gives that message, but there's too many
possible code paths (apparently) to pinpoint where this is happening...

But as you can't reproduce the bug now, it seems unlikely that we'll be
able to make further progress here.  If this happens again, try the
debug-on-message trick and open a new bug report, and post the
backtrace.  That should make it easier to track down.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.