From: Haider Rizvi <haider@nouce.ca.ibm.com>
Subject: Re: Invalid read syntax: "Integer constant overflow in reader"
Date: Mon, 29 Sep 2003 10:09:15 -0400 [thread overview]
Message-ID: <81wubrr8j8.fsf@thinkhr1.torolab.ibm.com> (raw)
In-Reply-To: <8165jbsoou.fsf@thinkhr1.torolab.ibm.com>
Replying to myself :-)
I resolved the problem by removing the cached articles and the whole
/d/News/agent/nntp/dbtnews.torolab.ibm.com/comp/databases/ibm-db2/
directory. I don't know what could have caused it to start with.
Haider Rizvi <haider@nouce.ca.ibm.com> writes:
> I am getting the following error while reading a newsgroup in gnus:
>
> Invalid read syntax: "Integer constant overflow in reader", "8387483875", 10
>
> I searched on google but there are very few instances of this error,
> some in Russian that I couldn't read and the others didn't have any
> solution. Any thoughts?
>
> Environment:
>
> Gnus v5.10.1
> XEmacs 21.4 (patch 13) "Rational FORTRAN" [Lucid] (i686-pc-cygwin) of Sun May 25 2003 on TSUNAMI
> 200 hanover.torolab.ibm.com InterNetNews NNRP server INN 2.3.3 ready (posting ok).
>
> Stack trace:
>
> Signaling: (invalid-read-syntax "Integer constant overflow in reader" "8387483875" 10)
> read(#<buffer " *nntpd*">)
> nnheader-find-nov-line(83916)
> gnus-agent-braid-nov("comp.databases.ibm-db2" (83916 83917 83918 83919 83920 83921 83938 83939 83940 83941 83942 83943 83944 83945 83946 83947 83948 83949 83950 83951) "/d/News/agent/nntp/dbtnews.torolab.ibm.com/comp/databases/ibm-db2/.overview")
> gnus-agent-retrieve-headers((83916 83917 83918 83919 83920 83921 83922 83923 83924 83925 83926 83927 83928 83929 83930 83931 83932 83933 83934 83935 83936 83937 83938 83939 83940 83941 83942 83943 83944 83945 83946 83947 83948 83949 83950 83951) "comp.databases.ibm-db2" nil)
> gnus-retrieve-headers((83916 83917 83918 83919 83920 83921 83922 83923 83924 83925 83926 83927 83928 83929 83930 83931 83932 83933 83934 83935 83936 83937 83938 83939 83940 83941 83942 83943 83944 83945 83946 83947 83948 83949 83950 83951) "comp.databases.ibm-db2" nil)
> gnus-cache-retrieve-headers((83916 83917 83918 83919 83920 83921 83922 83923 83924 83925 83926 83927 83928 83929 83930 83931 83932 83933 83934 83935 83936 83937 83938 83939 83940 83941 83942 83943 83944 83945 83946 83947 83948 83949 83950 83951) "comp.databases.ibm-db2" nil)
> gnus-retrieve-headers((83916 83917 83918 83919 83920 83921 83922 83923 83924 83925 83926 83927 83928 83929 83930 83931 83932 83933 83934 83935 83936 83937 83938 83939 83940 83941 83942 83943 83944 83945 83946 83947 83948 83949 83950 83951) "comp.databases.ibm-db2" nil)
> gnus-fetch-headers((83916 83917 83918 83919 83920 83921 83922 83923 83924 83925 83926 83927 83928 83929 83930 83931 83932 83933 83934 83935 83936 83937 83938 83939 83940 83941 83942 83943 83944 83945 83946 83947 83948 83949 83950 83951))
> gnus-select-newsgroup("comp.databases.ibm-db2" nil nil)
> gnus-summary-read-group-1("comp.databases.ibm-db2" nil nil nil nil nil)
> gnus-summary-read-group("comp.databases.ibm-db2" nil nil nil nil nil nil)
> gnus-group-read-group(nil)
> call-interactively(gnus-group-read-group)
--
Haider
next prev parent reply other threads:[~2003-09-29 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 13:34 Haider Rizvi
2003-09-29 14:09 ` Haider Rizvi [this message]
2003-09-29 20:07 ` Simon Josefsson
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=81wubrr8j8.fsf@thinkhr1.torolab.ibm.com \
--to=haider@nouce.ca.ibm.com \
/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).