From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: bug-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: bug#13701: 24.2.93; Segmentation fault
Date: Wed, 13 Feb 2013 21:00:56 +0100 [thread overview]
Message-ID: <86y5esc7bb.fsf@somewhere.org> (raw)
In-Reply-To: mailman.19842.1360777660.855.bug-gnu-emacs@gnu.org
Eli, Thierry,
Eli Zaretskii wrote:
>> From: Thierry Volpiatto <thierry.volpiatto-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Date: Wed, 13 Feb 2013 10:04:15 +0100
>> Cc: 13701-ubl+/3LiMTaZdePnXv/OxA@public.gmane.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
next prev parent reply other threads:[~2013-02-13 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 21:36 bug#13701: 24.2.93; Segmentation fault Sebastien Vauban
2013-02-13 2:53 ` Glenn Morris
2013-02-13 7:12 ` Thierry Volpiatto
[not found] ` <mailman.19776.1360739617.855.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.19776.1360739617.855.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-02-13 8:11 ` Sebastien Vauban
2013-02-13 9:04 ` Thierry Volpiatto
2013-02-13 17:47 ` Eli Zaretskii
[not found] ` <mailman.19842.1360777660.855.bug-gnu-emacs@gnu.org>
2013-02-13 20:00 ` Sebastien Vauban [this message]
[not found] ` <mailman.19796.1360746282.855.bug-gnu-emacs@gnu.org>
2013-02-13 9:16 ` Sebastien Vauban
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=86y5esc7bb.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=bug-gnu-emacs-mXXj517/zsQ@public.gmane.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).