Re: how to debug

[lee <lee@yun.yagibdah.de>]

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:
>>
>
> [...]
>> | 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...

Good to know that it doesn't seem to have bad effects :)

>> 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.

Hm, a while ago someone posted here who had a problem with connections
to news servers, too.

>> Is there a way to find out what gnus or emacs are doing when emacs is
>> busy?
> [...]
>
> 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.

Here's what I get:

,----
| Debugger entered--Lisp error: (quit)
|   signal(quit nil)
|   byte-code("\b\204\a.\301 \210\302\303\304\"\207" [debug-on-quit nntp-close-server signal quit nil] 3)
|   byte-code("\306\b	\n#\210\v\205.