Gnus development mailing list
 help / color / mirror / Atom feed
From: "Tassilo Horn" <tassilo@member.fsf.org>
To: "gnus mailing list" <ding@gnus.org>
Subject: Re: Debugger entered--Lisp error: (overflow-error "13419098521433281274")
Date: Wed, 02 Mar 2011 18:52:22 +0100	[thread overview]
Message-ID: <1299088342.7589.1425482829@webmail.messagingengine.com> (raw)
In-Reply-To: <87lj0x4k59.fsf@fastmail.fm>

Damn!  Now I get that error (with another big number) as soon as I try
to start Gnus.  I even don't get the group list anymore, so it's
rendering Gnus totally unfunctional for me. :-(

Any help?

Bye,
Tassilo

On Wed, 02 Mar 2011 16:28 +0100, "Tassilo Horn" <tassilo@member.fsf.org>
wrote:
> Hi all,
> 
> since a few minutes, I get this error when hitting `g' in *Group*.
> 
> --8<---------------cut here---------------start------------->8---
> Debugger entered--Lisp error: (overflow-error "13419098521433281274")
>   read(#<buffer *nnimap mail.messagingengine.com nil  *nntpd**>)
>   nnimap-parse-flags(...)
>   nnimap-finish-retrieve-group-infos(...)
>   gnus-finish-retrieve-group-infos(...)
>   gnus-read-active-for-groups(...)
>   gnus-get-unread-articles(nil)
>   gnus-group-get-new-news(nil)
>   call-interactively(gnus-group-get-new-news nil nil)
> --8<---------------cut here---------------end--------------->8---
> 
> That number is bigger than `most-positive-fixnum' on my 64bit system, so
> it cannot be `read'. :-(
> 
> The contents in that buffer around that number are as follows:
> 
> --8<---------------cut here---------------start------------->8---
> * OK [CLOSED] Ok
> * 2971 EXISTS
> * 1 RECENT
> * FLAGS (%Answered %Flagged %Draft %Deleted %Seen hasnoatt hasatt hasnotd
> hastd gnus-forward gnus-expire)
> * OK [PERMANENTFLAGS ()] Ok
> * OK [UNSEEN 2971] Ok
> * OK [UIDVALIDITY 1103381936] Ok
> * OK [UIDNEXT 12510] Ok
> * OK [HIGHESTMODSEQ 4858] Ok
> * OK [URLMECH INTERNAL] Ok
> * 2971 FETCH (FLAGS (%Recent) UID 12509 MODSEQ (13419098521433281274))
> 3901 OK [READ-WRITE] Completed
> * OK [CLOSED] Ok
> * 0 EXISTS
> * 0 RECENT
> --8<---------------cut here---------------end--------------->8---
> 
> Hm, after restarting gnus (which fetched several megabytes from that
> imap server), the issue seems to have vanished...  But I'm still
> interested what that number actually means?
> 
> Bye,
> Tassilo
> -- 
> Sent from my Emacs
> 
> 



  reply	other threads:[~2011-03-02 17:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 15:28 Tassilo Horn
2011-03-02 17:52 ` Tassilo Horn [this message]
2011-03-02 19:00 ` Andreas Schwab
2011-03-02 19:24   ` Tassilo Horn
2011-03-02 20:17     ` Ted Zlatanov
2011-03-02 20:36       ` Tassilo Horn
2011-03-02 20:52         ` Andreas Schwab
2011-03-02 21:02           ` Tassilo Horn
2011-03-02 20:56         ` Ted Zlatanov
2011-03-03  8:11           ` Tassilo Horn
2011-03-04 14:59             ` Ted Zlatanov
2011-03-05 10:52         ` Lars Magne Ingebrigtsen
2011-03-05 10:55 ` Lars Magne Ingebrigtsen
2011-03-07 17:29   ` Ted Zlatanov
2011-03-15 16:50     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1299088342.7589.1425482829@webmail.messagingengine.com \
    --to=tassilo@member.fsf.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).