Re: bug#13701: 24.2.93; Segmentation fault

[Sebastien Vauban]

Eli, Thierry,

Eli Zaretskii wrote:
>> From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
>> Date: Wed, 13 Feb 2013 10:04:15 +0100
>> Cc: 13701@debbugs.gnu.org
>> 
>> That say, probably Emacs should detect when calling a process if the
>> executable is compatible with value of `shell-file-name' and throw a big
>> old error if so before crashing Emacs, don't know if that is possible
>> though.
>
> It's not easy, at least.
>
>> (probably it is what Eli want to fix)
>
> Actually, I'm still trying to figure out what the heck happens on
> Sebastien's machine ;-)
>
> One problem with running programs via Bash or zsh is that these shells
> catch and ignore signals, and who knows what they do with Windows
> termination messages (which Emacs uses to kill subprocesses).  One
> other problem, which is specific to Windows, is that the
> TerminateProcess API does not kill child processes of the process we
> kill, so that killing a shell might leave the programs it runs in the
> system.  I see in Sebastien's reports that TerminateProcess is
> sometimes called, which might be a symptom of the problem (Emacs
> generally tries to avoid calling TerminateProcess, if it possibly
> can).

Just to add on the confusion, in the v24.2.91, 92 and 93, for sure, I'm do not
have ghost processes anymore (I don't remember the correct name): ones I had
to kill via ProcessExplorer (for example) to let Emacs respond again to me.

But... I cannot really say it's because of changes done in the dev versions,
as I happened to have a new, and fast, machine since beginning of January 2013
(Asus i7 laptop with 4 GB RAM and 256 GB SSD -- with Windows 8). So, if time
is a variable, time constraints definitely changed on my new system.

For the rest, nothing changed[1]: Emacs, Cygwin, and the good friends.

Best regards,
  Seb

[1] Even if my .emacs evolves weekly, if not daily ;-)

-- 
Sebastien Vauban