all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Sam Steingold <sds@gnu.org>
Cc: 41407@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	[thread overview]
Message-ID: <87o8nogsqr.fsf@gnus.org> (raw)
In-Reply-To: <m1tuxgrb40.fsf@gnu.org> (Sam Steingold's message of "Wed, 05 Aug 2020 18:17:35 -0400")

Sam Steingold <sds@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





      reply	other threads:[~2020-08-06  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 18:18 bug#41407: 28.0.50; infinite loop "Article 53570 has a nil data header" on "Exiting summary buffer and applying spam rules" Sam Steingold
2020-08-05 11:11 ` Lars Ingebrigtsen
2020-08-05 22:17   ` Sam Steingold
2020-08-06  7:04     ` Lars Ingebrigtsen [this message]

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=87o8nogsqr.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=41407@debbugs.gnu.org \
    --cc=sds@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.