From: Stephen Powell <stephen_powell@optusnet.com.au>
To: eliz@gnu.org
Cc: 13086@debbugs.gnu.org, eggert@cs.ucla.edu,
stephen_powell@optusnet.com.au
Subject: bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126
Date: Thu, 06 Dec 2012 22:51:16 +0000 [thread overview]
Message-ID: <50C12164.1030105@optusnet.com.au> (raw)
In-Reply-To: <50BEF635.4000702@optusnet.com.au>
Eli Zaretskii <eliz@gnu.org> writes:
> If the above doesn't show the light, can you please compile w32proc.c
> with -DFULL_DEBUG, and see what Emacs says about processes it launches
> and reaps when you run Emacs under GDB?
OK, its 9:30 my time and I got to do stuff, but here is what I've found
so for.
There are two hosts gnus connects to, Yahoo and HotMail.
1. Gnus uses the command
`c:\cygwin\bin\bash.exe -c "openssl s_client -quiet -ssl3 -connect
imap.mail.yahoo.com:993"'
which runs for a three or four seconds and exits with 0 as the return
code. Emacs keeps track of this process. Gnus seems to wait for this
to finish.
From the gdb log:
warning: register_child registered fd 6 with pid 6360
warning: sys_kill.TerminateProcess returned 5 for pid 6360
2. Gnus uses the command
`c:\cygwin\bin\bash.exe -c "gnutls-cli --insecure -p 995 pop3.live.com"'
which runs for fifty seconds and exits with 1 as the return code. Emacs
loses track of this process. Gnus does not seem to wait for this to
finish but carries on quickly.
From the gdb log:
warning: register_child registered fd 6 with pid 7020
No terminate process but the process has finished.
I'll try to get back to his latter today.
next prev parent reply other threads:[~2012-12-06 22:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 7:22 bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126 Stephen Powell
2012-12-05 16:42 ` Eli Zaretskii
2012-12-05 19:28 ` Stephen Powell
2012-12-05 21:25 ` Eli Zaretskii
2012-12-06 2:04 ` Paul Eggert
2012-12-06 3:51 ` Eli Zaretskii
2012-12-06 5:07 ` Paul Eggert
2012-12-06 18:28 ` Eli Zaretskii
2012-12-06 20:18 ` Paul Eggert
2012-12-06 20:25 ` Eli Zaretskii
2012-12-06 20:36 ` Paul Eggert
2012-12-06 20:39 ` Eli Zaretskii
2012-12-06 20:48 ` Eli Zaretskii
2012-12-06 21:36 ` Paul Eggert
2012-12-07 6:22 ` Eli Zaretskii
2012-12-07 17:54 ` Paul Eggert
2012-12-07 18:57 ` Eli Zaretskii
2012-12-06 20:57 ` Paul Eggert
2012-12-07 6:46 ` Eli Zaretskii
2012-12-07 16:48 ` Ken Brown
2012-12-07 17:43 ` Paul Eggert
2012-12-06 7:35 ` Paul Eggert
2012-12-06 18:41 ` Eli Zaretskii
2012-12-06 5:07 ` Stephen Powell
2012-12-06 19:10 ` Stephen Powell
2012-12-06 19:36 ` Eli Zaretskii
2012-12-06 19:48 ` Eli Zaretskii
2012-12-06 20:17 ` Stephen Powell
2012-12-06 20:36 ` Eli Zaretskii
2012-12-06 22:51 ` Stephen Powell [this message]
2012-12-07 6:43 ` Eli Zaretskii
2012-12-07 0:10 ` Stephen Powell
2012-12-07 6:44 ` Eli Zaretskii
2012-12-21 11:56 ` Eli Zaretskii
2012-12-23 17:12 ` Eli Zaretskii
2013-01-22 13:38 ` Eli Zaretskii
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=50C12164.1030105@optusnet.com.au \
--to=stephen_powell@optusnet.com.au \
--cc=13086@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.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.
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).