Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Need help: Where to debug "Server closed connection" opening Gmane NNTP groups with many unread articles on Windows?
Date: Wed, 28 Jan 2015 11:46:37 +0100	[thread overview]
Message-ID: <upzch9vb18tu.fsf@dod.no> (raw)
In-Reply-To: <871tmfwh7p.fsf@building.gnus.org>

>>>>> Lars Ingebrigtsen <larsi@gnus.org>:

> Steinar Bang <sb@dod.no> writes:
>> Since May last year, or thereabouts, I have seen a problem with git Gnus
>> on Win32, when opening Gmane NNTP groups with large number of unread
>> articles.
>> 
>> I plan to debug this now to find out where it actually breaks, but need
>> some pointers:
>> Where should I set a breakpoint? 

> You could perhaps try `debug-on-message'...

It seems to be fixed now, with a new emacs 24 (24.4 vs. 24.3) and a new
gnutls.dll from ezwinports.
 http://thread.gmane.org/gmane.emacs.help/101746/focus=101786

I reported something related to this as bug#16784
 http://comments.gmane.org/gmane.emacs.bugs/85764
that you reported as fixed with some new security stuff that will be a
part of emacs 25 (I think...?).
 http://permalink.gmane.org/gmane.emacs.bugs/97030




  reply	other threads:[~2015-01-28 10:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  7:06 Steinar Bang
2015-01-28  6:29 ` Lars Ingebrigtsen
2015-01-28 10:46   ` Steinar Bang [this message]
2015-09-07 19:51     ` Steinar Bang
2015-09-07 20:50       ` Andreas Schwab
2015-09-08 10:40         ` Steinar Bang
2015-09-08 17:47           ` Andreas Schwab
2015-09-10 20:24             ` Steinar Bang
2015-09-10 21:33               ` Andreas Schwab
2015-09-11  7:28                 ` Steinar Bang
2015-09-11  8:42                   ` Andreas Schwab
2015-09-11 10:54                     ` Steinar Bang
2015-09-11 15:20                       ` Eric Abrahamsen
2015-09-12  7:14                       ` Steinar Bang
2015-11-07  9:27                       ` Steinar Bang

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=upzch9vb18tu.fsf@dod.no \
    --to=sb@dod.no \
    --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).