From: Vincent Bernat <bernat@luffy.cx>
To: ding@gnus.org
Subject: Re: Activated two-part nntp async fetch again
Date: Wed, 02 Mar 2011 08:49:44 +0100 [thread overview]
Message-ID: <m3sjv6dkrr.fsf@neo.luffy.cx> (raw)
In-Reply-To: <87fwrikmgr.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 20 Feb 2011 21:04:04 -0800")
OoO En cette fin de nuit blanche du lundi 21 février 2011, vers 06:04,
Lars Ingebrigtsen <larsi@gnus.org> disait :
> I've now managed to reproduce the bug, and I think I've probably fixed
> it, but this is deep into obscure method uniquilisation (that should be
> a word) territory, so this may break other stuff. Or lead to having a
> lot of NNTP connections open.
Hi!
I am using b5fa82f9d758d5e39bf7c8908189c44759cb90b4 but I still get the
problem. Here is a backtrace:
nntp-with-open-group-function(nil "news.crans.org" nil #[nil "\306\b!\307 @@ @\"\310\311.^[.\211.\205\317.\x0e.\205\317.r.q\210\312.!\203L.\nb\210\313.\x19\2030.\314\2021.\315\316\317#\203=.\vT.\202&.`.\v.\x18W\203L.\320 \210\202.\0\321 \210.\x19\204}.ed{.\x1ar\bq\210\322 \210.^[\203l.\323.\x1a!\202n.\x0e.c\210eb\210*\324\f.\x1c\317#\202\316.eb\210\313\325\316\317#\203\223.\310\224\311y\210`|\210\202\200.ed{.\x1ar\bq\210\322 \210.^[\203\253.\323.\x1a!\202\255.\x0e.c\210eb\210*r\bq\210\326\327 @8:\203\307.\327 @8\202\310.\f.\x1c\316\317$)),\207" [nntp-server-buffer infos last-point received method buf nntp-find-connection-buffer gnus-find-method-for-group 0 1 gnus-buffer-live-p re-search-forward "^[.]" "^[0-9]" nil t nntp-accept-response nnheader-strip-cr erase-buffer mm-string-to-multibyte gnus-groups-to-gnus-format "^[.2-5]" gnus-active-to-gnus-format 4 count nntp-server-list-active-group string enable-multibyte-characters gnus-active-hashtb] 6])
nntp-finish-retrieve-group-infos("news.crans.org" (("nntp+news.crans.org:crans.crans" 3 (...) (... ... ... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.crans.annonces" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.general" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.informatique" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.dino" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.culture" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.informatique.linux" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.test" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.web-sympas" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:tac.bde" 3 (...) (...) "nntp:news.crans.org" (...))) 10)
gnus-finish-retrieve-group-infos((nntp "news.crans.org") (("nntp+news.crans.org:crans.crans" 3 (...) (... ... ... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.crans.annonces" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.general" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.informatique" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.dino" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.culture" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.informatique.linux" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.test" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.web-sympas" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:tac.bde" 3 (...) (...) "nntp:news.crans.org" (...))) 10)
gnus-read-active-for-groups((nntp "news.crans.org") (("nntp+news.crans.org:crans.crans" 3 (...) (... ... ... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.crans.annonces" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.general" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.informatique" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.dino" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.culture" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.informatique.linux" 3 (...) (... ...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.test" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:crans.web-sympas" 3 (...) (...) "nntp:news.crans.org" (...)) ("nntp+news.crans.org:tac.bde" 3 (...) (...) "nntp:news.crans.org" (...))) 10)
--
Make input easy to proofread.
- The Elements of Programming Style (Kernighan & Plauger)
next prev parent reply other threads:[~2011-03-02 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 21:22 Lars Ingebrigtsen
2011-02-15 11:43 ` Eric Abrahamsen
2011-02-18 23:20 ` Lars Ingebrigtsen
2011-02-21 5:04 ` Lars Ingebrigtsen
2011-03-02 7:49 ` Vincent Bernat [this message]
2011-03-05 10:57 ` Lars Magne Ingebrigtsen
2011-03-19 10:35 ` Eric Abrahamsen
2011-03-29 20:22 ` Lars Magne Ingebrigtsen
2011-03-30 1:11 ` Eric Abrahamsen
2011-04-12 16:48 ` Lars Magne Ingebrigtsen
2011-02-16 17:41 ` Manoj Srivastava
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=m3sjv6dkrr.fsf@neo.luffy.cx \
--to=bernat@luffy.cx \
--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).