From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Powell <stephen_powell@optusnet.com.au>,
Paul Eggert <eggert@cs.ucla.edu>
Cc: 13086@debbugs.gnu.org
Subject: bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126
Date: Wed, 05 Dec 2012 23:25:54 +0200 [thread overview]
Message-ID: <83r4n4p4wt.fsf@gnu.org> (raw)
In-Reply-To: <50BFA054.1060503@optusnet.com.au>
> Date: Wed, 05 Dec 2012 19:28:20 +0000
> From: Stephen Powell <stephen_powell@optusnet.com.au>
> CC: stephen_powell@optusnet.com.au, 13086@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Can you use the 'finish' command, as described in etc/DEBUG, to find
> > out where it loops?
>
> (gdb) thread 1
> [Switching to thread 1 (Thread 7752.0x1bb0)]
> #0 waitpid (pid=5528, status=0x0, options=1) at w32proc.c:1126
> 1126 {
> (gdb) finish
> Run till exit from #0 waitpid (pid=5528, status=0x0, options=1) at
> w32proc.c:1126
> 0x010e04ab in get_child_status (child=5528, status=0x0, options=1,
> interruptible=false)
> at sysdep.c:290
> 290 while ((pid = waitpid (child, status, options)) < 0)
> Value returned is $1 = -1
> (gdb) finish
> Run till exit from #0 0x010e04ab in get_child_status (child=5528,
> status=0x0, options=1,
> interruptible=false) at sysdep.c:290
>
> Hung here.
I see. I wonder why it returned -1 the first time, when the process
was still running or just exited. Can you try setting breakpoints in
a way that will be able to explain that?
I also don't understand the logic of the loop in get_child_status.
Paul, can you tell why it loops if waitpid is called with WNOHANG and
returns -1? Won't that cause a busy-wait loop that pegs the CPU?
next prev parent reply other threads:[~2012-12-05 21:25 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r4n4p4wt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13086@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=stephen_powell@optusnet.com.au \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.