From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: error fetching emails in agent
Date: Tue, 12 Apr 2011 18:45:32 +0200 [thread overview]
Message-ID: <m3aafvifkj.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87pqp7r8yb.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> finally, yes! I have had debug-on-error turned on and have been trying
> Js periodically the past day or two and finally I got an error with
> corresponding backtrace:
> Debugger entered--Lisp error: (args-out-of-range 13294 19274)
> gnus-agent-fetch-articles("nnimap+ucl:lists.org" (2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ...))
[...]
> However, I don't think it's particularly helpful.
No, unfortunately that function is really, really long, so it's
difficult to say what's going on. Running with an uncompiled
gnus-agent.el will give a more detailed backtrace.
> I think I've narrowed down the conditions under which this happens: if I
> read a group and exit it, with articles being expired as a result, and
> then ask the agent to fetch articles without saving first, this seems to
> happen. If I save ('s' in Group buffer), this doesn't seem to happen or
> if no articles have been expired since the last save it doesn't seem to
> happen either.
Hm... I've looked at what `s' does, and I can't quite see how that
would interfere with the Agent, one way or other.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2011-04-12 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 14:50 Eric S Fraga
2011-03-29 18:37 ` Lars Magne Ingebrigtsen
2011-03-31 8:27 ` Eric S Fraga
2011-04-12 16:45 ` Lars Magne 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=m3aafvifkj.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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.
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).