Re: Debugger entered--Lisp error: (overflow-error "13419098521433281274")

[Tassilo Horn <tassilo@member.fsf.org>]

Ted Zlatanov <tzz@lifelogs.com> writes:

Hi Ted,

>>> To fix it now, I would replace such large numbers with a truncated
>>> version, which can be done safely with a regex before the reader
>>> sees the input.  But I'll let Lars decide, he knows that code best.
>
> TH> But that huge number is not used by gnus, anyway.  It is `read'
> TH> but only the UID and FLAGS values are saved.  So IMHO, the proper
> TH> fix is to put a condition-case around the `read' that picks the
> TH> UID and FLAGS with string-matching if an overflow-error occurs.
>
> Yeah, that would work too, but it's a hack either way.  My way would
> be less work since we just rewrite that number to 1 or whatever, which
> is one extra line of code.  If you want to submit a patch for either
> hack go ahead, otherwise I'll wait for Lars to fix it.

I've now combined both approaches.  A condition-case handler simply
deletes the big number and `read's again.  That fixes the issue for me.
I added a FIXME and comment, too.  Maybe Lars has some better idea how
to deal with that.

Since that number occurs as value of MODSEQ (which Gnus doesn't use), is
the HIGHESTMODSEQ (which Gnus reads and stores as number) also a
candidate for overflowing?  It probably is, so it might be better to
handle it as string just like the UIDVALIDITY.

Bye,
Tassilo
-- 
Sent from my Emacs