unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 5723@debbugs.gnu.org, Helmut Eller <eller.helmut@gmail.com>
Subject: bug#5723: 23.1.94; make-network-process and emacs hangs
Date: Wed, 17 Mar 2010 12:01:16 +0000	[thread overview]
Message-ID: <xbaiwrxbdunn.fsf@cam.ac.uk> (raw)
In-Reply-To: <wlhbohksbr.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Tue, 16 Mar 2010 09:45:12 +0900")

On 2010-03-16 00:45 +0000, YAMAMOTO Mitsuharu wrote:
>> make-network-process calls getaddrinfo and C-g doesn't work properly
>> during that call.  It's only observable if the name server is slow
>> or misconfigured.
>
>> glibc has a asynchronous variant getaddrinfo_a (in libanl.so) which
>> uses threads internally and quickly passes control back to the
>> caller.  That could be used on GNU/Linux but the OP uses a Mac.
>
> I guess OP's case is about `connect' rather than `getaddrinfo'.
>
>   http://lists.gnu.org/archive/html/emacs-devel/2009-08/msg00148.html
>
> Leo, can you check where it blocks (using GDB), and whether giving
> --without-sync-input as a configure option changes the situation
> (using the X11 build, preferably)?

With this option and build emacs with X11, I can't start the gui
version, getting this error:

Xlib: unexpected async reply (sequence 0x5c)!

Starting emacs with emacs -nw I can quit with C-g nicely. 

I have no luck with --with-mac, C-g still can not stop the process.

Leo






  reply	other threads:[~2010-03-17 12:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 16:01 bug#5723: 23.1.94; make-network-process and emacs hangs Leo
2010-03-15 18:24 ` Dan Nicolaescu
2010-03-15 19:22 ` Stefan Monnier
2010-03-15 22:49   ` Helmut Eller
2010-03-16  0:45     ` YAMAMOTO Mitsuharu
2010-03-17 12:01       ` Leo [this message]
2010-03-18  1:57         ` YAMAMOTO Mitsuharu
2010-03-18  7:43           ` Helmut Eller
2010-03-18  9:06             ` YAMAMOTO Mitsuharu
2010-03-19  1:47               ` YAMAMOTO Mitsuharu
2010-03-19  6:41                 ` Helmut Eller
2010-03-19 10:21                   ` YAMAMOTO Mitsuharu
2010-03-19 13:29                     ` Stefan Monnier
2010-03-20  0:30                       ` YAMAMOTO Mitsuharu
2010-03-20 12:34                     ` Leo
2010-03-24 22:00                     ` Chong Yidong
2010-03-24 23:31                       ` YAMAMOTO Mitsuharu
2010-03-25  1:25                         ` Chong Yidong
2010-03-18  9:58           ` Leo
2010-03-18  2:20         ` YAMAMOTO Mitsuharu
2010-03-18 10:00           ` Leo
2010-03-18 10:37             ` YAMAMOTO Mitsuharu
2010-03-18 10:47               ` Leo
2010-03-18 11:01                 ` YAMAMOTO Mitsuharu
2010-03-17 11:53   ` Leo
2010-03-25  9:00 ` bug#5723: (no subject) YAMAMOTO Mitsuharu

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=xbaiwrxbdunn.fsf@cam.ac.uk \
    --to=sdl.web@gmail.com \
    --cc=5723@debbugs.gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).