unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Bellmann, Andreas" <abellmann@heiler.com>
Cc: 11849@debbugs.gnu.org
Subject: bug#11849: AW: AW: bug#11849: 23.3; emacs freeze when vpn is connected
Date: Fri, 20 Jul 2012 11:33:36 +0300	[thread overview]
Message-ID: <83d33q96hr.fsf@gnu.org> (raw)
In-Reply-To: <25717D3244A1944A8A4152BE37B493B523421BC8@HSMSX03.iheiler.com>

> From: "Bellmann, Andreas" <abellmann@heiler.com>
> CC: "11849@debbugs.gnu.org" <11849@debbugs.gnu.org>
> Date: Fri, 20 Jul 2012 07:55:05 +0000
> Unfortunately not. This setting has been active for a while now without any improvement.
> 
> Any other ideas?

The only other idea I have is to somehow find out which code in Emacs
causes the stall.  If you can build your own Emacs and step through it
with a debugger, I can suggest where to look.

Alternatively, try using some tool that shows Windows API calls issued
by Emacs together with their responses, and see if that info shows
which API call stalls.  We could then try finding the Emacs code that
results in calling that API.





  reply	other threads:[~2012-07-20  8:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  8:46 bug#11849: 23.3; emacs freeze when vpn is connected Bellmann, Andreas
2012-07-03 16:40 ` Eli Zaretskii
2012-07-04  8:55   ` bug#11849: AW: " Bellmann, Andreas
2012-07-04 15:24     ` Eli Zaretskii
2012-07-04 16:21       ` Bellmann, Andreas
2012-07-04 16:46         ` Eli Zaretskii
2012-07-06  9:14           ` bug#11849: AW: " Bellmann, Andreas
2012-07-11 15:52             ` Bellmann, Andreas
2012-07-11 17:43               ` Eli Zaretskii
2012-07-20  7:55                 ` bug#11849: AW: " Bellmann, Andreas
2012-07-20  8:33                   ` Eli Zaretskii [this message]
2012-07-20  8:48                     ` Eli Zaretskii
2019-09-26 15:08 ` Stefan Kangas
2019-09-26 15:09   ` Stefan Kangas

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83d33q96hr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11849@debbugs.gnu.org \
    --cc=abellmann@heiler.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).