From: egallego@babel.ls.fi.upm.es (Emilio Jesús Gallego Arias)
To: ding@gnus.org
Subject: Re: How to debug hangs during message fetching
Date: Tue, 15 Feb 2011 22:28:51 +0100 [thread overview]
Message-ID: <87d3mtng18.fsf@babel.ls.fi.upm.es> (raw)
In-Reply-To: <87oc6fvunf.fsf@member.fsf.org>
After a pull today I'm getting fairly similar hangs, I'm not using
daemon or anything fancy, the hang just happens when starting gnus.
I'm using current git master, I've bisected and this commit seems the
culprit:
$ git bisect bad
894b2ac5b356510bd62b23597abc20badb7b27e8 is the first bad commit
commit 894b2ac5b356510bd62b23597abc20badb7b27e8
Author: Lars Ingebrigtsen <larsi@gnus.org>
Date: Thu Feb 3 07:36:03 2011 -0800
Request active files from primary/secondary methods that have no groups (yet).
:040000 040000 b309a842a98585ed43219e9e944ffb753506d9f7 4a2ea41728c86e5a3beb3fe8203d5dbb82ee0428 M lisp
Backing out that particular change in top of current head fixes the hang
for me.
This happens in a dovecot server using nnimap. It happens at start and
whenever I press g or M-g. Then I need to press C-g in order to get out
of the hang. debug-on-quit does not work.
Regarding the buffer contents:
,----[ imap log: ]
| 22:16:07 679 EXAMINE "#mailman.slam"
| 22:16:07 680 EXAMINE "#mailman.mtp-dev"
`----
,----[ *nnimap buffer*: ]
| 679 OK [READ-ONLY] Select completed.
| * OK [CLOSED] Previous mailbox closed.
| * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
| * OK [PERMANENTFLAGS ()] Read-only mailbox.
| * 3350 EXISTS
| * 0 RECENT
| * OK [UIDVALIDITY 1257814760] UIDs valid
| * OK [UIDNEXT 3351] Predicted next UID
| * OK [HIGHESTMODSEQ 2] Highest
| 680 OK [READ-ONLY] Select completed.
|
| Process *nnimap* terminado (killed)
`----
,----[ relevant gnus config: ]
|
| (setq gnus-select-method '(nntp "news.gmane.org"
| (nntp-address "news.gmane.org")))
|
| (setq gnus-secondary-select-methods
| '((nnimap "dovecot"
| (nnimap-address "dovecot")
| (nnimap-stream ssl))))
|
| (setq nnimap-inbox "INBOX")
| (setq nnimap-split-crosspost t)
| (setq nnimap-split-methods 'default)
| (setq nnmail-split-methods 'nnmail-split-fancy)
| (setq nnmail-split-fancy ...)
`----
Regards,
Emilio
next prev parent reply other threads:[~2011-02-15 21:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:31 Tassilo Horn
2011-02-07 11:44 ` Lars Ingebrigtsen
2011-02-07 11:55 ` Tassilo Horn
2011-02-07 11:59 ` Lars Ingebrigtsen
2011-02-07 12:17 ` Tassilo Horn
2011-02-07 12:21 ` Lars Ingebrigtsen
2011-02-07 12:39 ` Tassilo Horn
2011-02-07 12:57 ` Tassilo Horn
2011-02-14 3:35 ` Lars Ingebrigtsen
2011-02-14 9:21 ` Tassilo Horn
2011-02-15 21:28 ` Emilio Jesús Gallego Arias [this message]
2011-02-16 22:12 ` Lars Ingebrigtsen
2011-02-16 22:18 ` Emilio Jesús Gallego Arias
2011-02-16 22:24 ` Lars Ingebrigtsen
2011-02-17 0:27 ` Emilio Jesús Gallego Arias
2011-02-17 23:48 ` Lars Ingebrigtsen
2011-02-23 2:12 ` Emilio Jesús Gallego Arias
2011-02-23 2:18 ` Emilio Jesús Gallego Arias
2011-02-23 9:04 ` Lars Ingebrigtsen
2011-02-24 2:18 ` Emilio Jesús Gallego Arias
2011-02-25 3:33 ` Lars Ingebrigtsen
2011-02-19 9:45 ` Vincent Bernat
2011-02-20 1:22 ` Lars Ingebrigtsen
2011-02-20 13:14 ` Vincent Bernat
2011-02-07 21:21 ` Ludovic Courtès
2011-02-07 21:27 ` Michael Welsh Duggan
2011-02-14 3:35 ` Lars Ingebrigtsen
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=87d3mtng18.fsf@babel.ls.fi.upm.es \
--to=egallego@babel.ls.fi.upm.es \
--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).