From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/83787 Path: news.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Re: How to get this debugged (pressing g fails) Date: Fri, 27 Sep 2013 17:23:48 -0400 Organization: Still searching... Message-ID: <87zjqydkm3.fsf@newsguy.com> References: <871u4cwiwu.fsf@newsguy.com> <87ioxngx9b.fsf@newsguy.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1380317100 27153 80.91.229.3 (27 Sep 2013 21:25:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Sep 2013 21:25:00 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M32043@lists.math.uh.edu Fri Sep 27 23:25:03 2013 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VPfX3-0000GF-VG for ding-account@gmane.org; Fri, 27 Sep 2013 23:25:02 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1VPfWC-0002ty-8Z; Fri, 27 Sep 2013 16:24:08 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1VPfWA-0002tj-Oe for ding@lists.math.uh.edu; Fri, 27 Sep 2013 16:24:06 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1VPfW8-0007rF-Fb for ding@lists.math.uh.edu; Fri, 27 Sep 2013 16:24:05 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1VPfW6-0001ju-Ho for ding@gnus.org; Fri, 27 Sep 2013 23:24:02 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VPfW5-0007vw-9G for ding@gnus.org; Fri, 27 Sep 2013 23:24:01 +0200 Original-Received: from z65-50-57-227.ips.direcpath.com ([65.50.57.227]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 27 Sep 2013 23:24:01 +0200 Original-Received: from reader by z65-50-57-227.ips.direcpath.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 27 Sep 2013 23:24:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 58 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: z65-50-57-227.ips.direcpath.com User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.0.92 (gnu/linux) Cancel-Lock: sha1:WepXjhdED+lOoJtZLDW08CEzNQ8= X-Spam-Score: -4.3 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:83787 Archived-At: Katsumi Yamaoka 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] 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.