From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: how to debug
Date: Thu, 07 Jul 2011 08:52:33 +0200 [thread overview]
Message-ID: <878vsa60r2.fsf@member.fsf.org> (raw)
In-Reply-To: <87oc166h9p.fsf@yun.yagibdah.de> (lee@yun.yagibdah.de's message of "Thu, 07 Jul 2011 02:55:46 +0200")
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.
> Is there a way to find out what gnus or emacs are doing when emacs is
> busy? I've already "(setq debug-on-error t)" in ~/.emacs. A bug
> report like this probably isn't useful at all, so it would be nice if
> I could provide some more information.
Set debug-on-quit instead. Then you are put into the debugger on C-g
and you can figure out what function was executing when the freeze
occured.
> As to the TLS error: I'm not aware of using TLS. I have an ~/.authinfo
> file for one of the news servers, though.
I think Gnus uses TLS by default if the server supports it.
Bye,
Tassilo
--
Sent from my Emacs
next prev parent reply other threads:[~2011-07-07 6:52 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 [this message]
2011-07-07 8:57 ` Leonidas Tsampros
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=878vsa60r2.fsf@member.fsf.org \
--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).