From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 13086@debbugs.gnu.org, 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:39:33 +0200 [thread overview]
Message-ID: <83y5haoqyi.fsf@gnu.org> (raw)
In-Reply-To: <50C101B5.40705@cs.ucla.edu>
> Date: Thu, 06 Dec 2012 12:36:05 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: stephen_powell@optusnet.com.au, 13086@debbugs.gnu.org
>
> On 12/06/12 12:25, Eli Zaretskii wrote:
>
> > How can that happen, if PID is not our child process?
>
> Because Emacs regularly kills processes that it thinks are its
> children. If I'm running several applications, one of them
> can kill the other even if the applications are otherwise
> unrelated -- that's standard Unix semantics. So if
> Emacs mistakenly thinks that it has a child with PID 1234
> and does the equivalent of "kill -9 1234", which is something
> that delete-process does, Emacs can kill an innocent and
> unrelated victim.
But that already happened when we are calling waitpid. It cannot be
helped at that point.
> >> One possibility is for Emacs to fall back into recovery mode
> >
> > It is much easier to remove the offending process object from the list
> > of those we expect to be dead.
>
> Sure, but there's a good case for being cautious here, even if
> it's a bit harder to be cautious.
It doesn't make sense to be that cautious in an Emacs compiled without
assertions.
next prev parent reply other threads:[~2012-12-06 20:39 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 [this message]
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=83y5haoqyi.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.