From: Leonidas Tsampros <ltsampros@upnet.gr>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: ding@gnus.org
Subject: Re: how to debug
Date: Thu, 07 Jul 2011 11:57:59 +0300 [thread overview]
Message-ID: <87vcvexsln.fsf@kepler.lan> (raw)
In-Reply-To: <878vsa60r2.fsf@member.fsf.org>
Tassilo Horn <tassilo@member.fsf.org> writes:
> lee <lee@yun.yagibdah.de> writes:
>
> Hi!
>
>> with emacs 24 from tonight, gnus sometimes keeps emacs busy
>> indefinitely when checking for new news (pressing `g' in the group
>> buffer). I'm getting messages like:
>>
>> ,---- [ *Messages* ]
>> | Checking new news...
>> | Reading active file from diary via nndiary...
>> | Opening nndiary server on diary...done
>> | Reading incoming mail from file...
>> | nndiary: Reading incoming mail (no new mail)...done
>> | Reading active file from diary via nndiary...done
>> | gnutls.c: [0] (Emacs) fatal error: A TLS packet with unexpected length was received.
>
> I get that error twice a day, too. But it doesn't seem to have any bad
> effect...
>
>> | Reading active file from yun via nnml...
>> | Reading incoming mail from file... [2 times]
>> | Reading incoming mail from maildir...
>> | Wrote /home/lee/Mail/mail/lists/mythtv-users/9043
>> | Wrote /home/lee/Mail/mail/lists/mythtv-users/9044
>> | Wrote /home/lee/Mail/mail/lists/debian-user/96166
>> | [...]
>> | Wrote /home/lee/Mail/mail/lists/debian-user/96168
>> | nnml: Reading incoming mail (21 new)...done
>> | Reading active file from yun via nnml...done
>> | Quit
>> `----
>>
>> When I press Ctrl-g, emacs isn't busy anymore. I can even check for
>> news again, and it eventually works fine.
>
> I can observe a similar behavior since month. Usually, the last output
> is "nnimap read 78k" and then it stalls until I hit C-g. After that,
> all works fine again.
I can confirm this too! Using yesterday's emacs 24, and a pop3 mail
source I can confirm the exact same behaviour. It randomly stays stuck
while reading mail from the pop3 server. Pressing C-g and g to get the
news again eventually works fine with no bad side effects.
Setting debug-on-quit to t, I caught this but it's probably not enough:
Debugger entered--Lisp error: (quit)
pop3-accept-process-output(#<process POP>)
pop3-wait-for-messages(#<process POP> 22 175976)
pop3-send-streaming-command(#<process POP> "RETR" 22 175976)
pop3-movemail("~/.emacs-mail-crash-box")
mail-source-fetch-pop((pop :server "mail.popserver.com" :user "ltsampros" :password "password") #[(file orig-file) "\303\b\304\305 \206\b\n\232?\205\306\n\307\"\310%\207" [file in-group orig-file nnmail-split-incoming nnml-save-mail nil nnmail-get-split-group (pop :server "mail.popserver.com" :user "ltsampros" :password "password") nnml-active-number] 7])
mail-source-fetch((pop :server "mail.popserver.com" :user "ltsampros" :password "password") #[(file orig-file) "\303\b\304\305 \206\b\n\232?\205\306\n\307\"\310%\207" [file in-group orig-file nnmail-split-incoming nnml-save-mail nil nnmail-get-split-group (pop :server "mail.popserver.com" :user "ltsampros" :password "password") nnml-active-number] 7])
nnmail-get-new-mail-1(nnml nnml-save-incremental-nov "~/Mail.Gnus" nil nil nil)
nnmail-get-new-mail(nnml nnml-save-incremental-nov "~/Mail.Gnus" nil)
nnml-request-scan(nil "")
gnus-request-scan(nil (nnml ""))
gnus-read-active-file-1((nnml "") nil)
gnus-read-active-for-groups((nnml "") (many-many-many data here)
gnus-get-unread-articles(nil)
gnus-setup-news(nil nil nil)
byte-code("\b\204 \204\306 \210\202L\307\310!\210\311\n!\f\204\203!\312 \210\313\314\b#\210\307\315!\210\2036\316\317\320\"\210\321 \210\322!\210\323 \210\324\325!\210\326 \210\307\327!\210\314\207" [dont-connect did-connect gnus-startup-file gnus-current-startup-file gnus-slave gnus-use-dribble-file gnus-group-quit gnus-run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-dribble-read-file gnus-setup-news nil gnus-setup-news-hook gnus-request-create-group "queue" (nndraft "") gnus-start-draft-setup gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook level gnus-agent] 4)
gnus-1(nil nil nil)
gnus(nil)
call-interactively(gnus t nil)
execute-extended-command(nil)
call-interactively(execute-extended-command nil nil)
Best Regards,
Leonidas Tsampros
[...]
next prev parent reply other threads:[~2011-07-07 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 0:55 lee
2011-07-07 6:52 ` Tassilo Horn
2011-07-07 8:57 ` Leonidas Tsampros [this message]
2011-07-07 15:03 ` lee
2011-07-19 16:36 ` Lars Magne Ingebrigtsen
2011-07-20 19:16 ` Leonidas Tsampros
2011-07-20 19:30 ` Lars Magne Ingebrigtsen
2011-07-21 0:26 ` Leonidas Tsampros
2011-08-21 3:52 ` Lars Magne Ingebrigtsen
2011-07-07 14:35 ` lee
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=87vcvexsln.fsf@kepler.lan \
--to=ltsampros@upnet.gr \
--cc=ding@gnus.org \
--cc=tassilo@member.fsf.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).