Gnus development mailing list
 help / color / mirror / Atom feed
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: Thu, 17 Feb 2011 01:27:34 +0100	[thread overview]
Message-ID: <87fwrnfqtl.fsf@babel.ls.fi.upm.es> (raw)
In-Reply-To: <87ipwjpqhf.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> egallego@babel.ls.fi.upm.es (Emilio Jesús Gallego Arias) writes:

>> Sorry Lars, should I do this with the code enabled (hang happens) or
>> with the code commented out?
>>
>> Keep in mind that #mailman.mtp-dev is read-only IMAP group.
>
> When the hang happens, I think, but both might be interesting.

This is with the code commented out (no hang):

00:52:56 396 EXAMINE "#mailman.mtp-dev"

* 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
396 OK [READ-ONLY] Select completed.

This is with the code enabled (as it is in the git repos)

01:24:39 218 EXAMINE "#mailman.mtp-dev"

* 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
218 OK [READ-ONLY] Select completed.

Virtually identical...

Regards,
Emilio




  reply	other threads:[~2011-02-17  0:27 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
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 [this message]
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=87fwrnfqtl.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).