[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126
From: |
Eli Zaretskii |
Subject: |
bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126 |
Date: |
Thu, 06 Dec 2012 22:39:33 +0200 |
> 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.
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, (continued)
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/05
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Stephen Powell, 2012/12/05
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/05
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/05
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/05
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/06
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/06
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/06
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/06
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/06
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126,
Eli Zaretskii <=
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/06
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/06
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/07
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/07
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/07
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/06
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Eli Zaretskii, 2012/12/07
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Ken Brown, 2012/12/07
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/07
- bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126, Paul Eggert, 2012/12/06