From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: How to get this debugged (pressing g fails)
Date: Fri, 27 Sep 2013 17:23:48 -0400 [thread overview]
Message-ID: <87zjqydkm3.fsf@newsguy.com> (raw)
In-Reply-To: <b4mtxh7p599.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
[...]
>> from Messages buffer
> ,----
> | Checking new news...
> | nnimap read 2k from imap.gmail.com
> | Reading active file via nnml...
> | Reading incoming mail from directory...
> | Wrote /home/reader/Mail/mail_cron_tr/30553
> | Wrote /home/reader/Mail/mail_rsnap_tr/13838
> | Reading incoming mail from file...
> | nnml: Reading incoming mail (2 new)...done
> | Reading active file via nnml...done
> | Reading active file from archive via nnfolder...done
> | Reading active file via nndraft...done
> | Gnus timed out.
> ^^^^^^^^^^^^^^
> | Entering debugger...
> `----
>
> Grep doesn't hit such a words combination in the Gnus source or
> the Emacs source, but Google does. For instance, bitbucket[1]
> shows this:
>
> (defadvice gnus-group-get-new-news (around gnus-timeout activate)
> "Timeout for Gnus."
> (with-timeout
> (5 (message "Gnus timed out.") (debug))
> ad-do-it))
>
> Do you have the one like that in your ~/.gnus.el file? If so,
> too small timeout seconds (5 in that case) may cause the problem.
>
> [1] <https://bitbucket.org/kindahero/emacsd/src/9a4c7b1e85a3ee9e80ca53f32260a6bc36e90f8a/init-gnus.el>
Haa, you got it Katsumi. Now I remember a good while back being
disgusted with long stalls from gnus and so thought I was being very
clever by putting that code in .gnus, making gnus fail and tell me
why. Instead of just setting there endlessly.
Over time I forgot all about it.
Thank you for investigating and hitting pay dirt.
A simple 5 second increase, up to 10 seconds solved the problem and
maybe I'll even remember it for a while now.
But more than anything, thanks for letting me watch HOW you
investigated the few clues I provided.
It all looks very simple seeing you do it, but I would probably never
have thought to follow the clues so well.
The technique is worth a lot. And I expect keeping it in mind when
doing other debugging chores (even in other scripting or languages)
will stand me in good stead. Again, thanks.
next prev parent reply other threads:[~2013-09-27 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 0:01 Harry Putnam
2013-09-26 0:50 ` Katsumi Yamaoka
2013-09-26 20:10 ` Harry Putnam
2013-09-26 22:50 ` Katsumi Yamaoka
2013-09-27 21:23 ` Harry Putnam [this message]
2013-10-01 14:56 ` Harry Putnam
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=87zjqydkm3.fsf@newsguy.com \
--to=reader@newsguy.com \
--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).