GNU bug report logs - #13701
24.2.93; Segmentation fault

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 13701 in the body.
You can then email your comments to 13701 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Sebastien Vauban" <wxhgmqzgwmuf <at> spammotel.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.2.93; Segmentation fault
Date: Tue, 12 Feb 2013 22:36:18 +0100

Eli,

When answering your latest post, I got a segfault, and Emacs completely
crashed:

--8<---------------cut here---------------start------------->8---
warning: sys_read called when read is in progress
[New Thread 15276.0x17cc]


Program received signal SIGSEGV, Segmentation fault.
0x00000213 in ?? ()
(gdb)
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00000213 in ?? ()
(gdb) continue
Continuing.
[New Thread 15276.0x6638]
[Inferior 1 (process 15276) exited with code 0377]
(gdb)
--8<---------------cut here---------------end--------------->8---

Best regards,
  Seb

-- 
Sebastien Vauban

Message #8 received at 13701 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: "Sebastien Vauban" <wxhgmqzgwmuf <at> spammotel.com>
Cc: 13701 <at> debbugs.gnu.org
Subject: Re: bug#13701: 24.2.93; Segmentation fault
Date: Tue, 12 Feb 2013 21:53:36 -0500

"Sebastien Vauban" wrote:

> warning: sys_read called when read is in progress

Searching for this message, I found that the only hit is crashes
previously reported by you in Emacs 24.1 and 24.2:

http://lists.gnu.org/archive/html/help-gnu-emacs/2012-10/msg00021.html

So maybe the issue(s) is not new and is caused by some unusual
circumstance on your machine.

> Program received signal SIGSEGV, Segmentation fault.
> 0x00000213 in ?? ()

I'm going to go out on a limb and say that more information will be
needed to solve this...

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#13701: 24.2.93; Segmentation fault
Date: Wed, 13 Feb 2013 08:12:13 +0100

Glenn Morris <rgm <at> gnu.org> writes:

> "Sebastien Vauban" wrote:
>
>> warning: sys_read called when read is in progress
>
> Searching for this message, I found that the only hit is crashes
> previously reported by you in Emacs 24.1 and 24.2:
>
> http://lists.gnu.org/archive/html/help-gnu-emacs/2012-10/msg00021.html
>
> So maybe the issue(s) is not new and is caused by some unusual
> circumstance on your machine.
The initial problem was the user is setting `shell-file-name' to
"/path/to/bash" on a windows machine where the value is normally
"/path/to/cmdproxy.exe".
The result is that all externals programs made to be used with
"cmdproxy.exe" are crashing Emacs.
In the case of `helm', the user is crashing Emacs with the helm-locate
command which use the executable "es.exe" which is part of "everything"
program.
So I think these crash are not the fault of Emacs nor helm, but a bad
setting of user.

So the question is:
Sebastien, are you still using shell-file-name==bash in your config ?

>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00000213 in ?? ()
>
> I'm going to go out on a limb and say that more information will be
> needed to solve this...
>
>
>
>

-- 
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

Message #14 received at 13701 <at> debbugs.gnu.org (full text, mbox):

From: "Sebastien Vauban" <wxhgmqzgwmuf <at> spammotel.com>
To: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
Cc: 13701 <at> debbugs.gnu.org
Subject: Re: bug#13701: 24.2.93; Segmentation fault
Date: Wed, 13 Feb 2013 09:11:49 +0100

Hi Thierry, Glenn and all,

Thierry Volpiatto wrote:
> Glenn Morris <rgm <at> gnu.org> writes:
>> "Sebastien Vauban" wrote:
>>
>>> warning: sys_read called when read is in progress
>>
>> Searching for this message, I found that the only hit is crashes
>> previously reported by you in Emacs 24.1 and 24.2:
>>
>> http://lists.gnu.org/archive/html/help-gnu-emacs/2012-10/msg00021.html
>>
>> So maybe the issue(s) is not new and is caused by some unusual
>> circumstance on your machine.
>
> The initial problem was the user is setting `shell-file-name' to
> "/path/to/bash" on a windows machine where the value is normally
> "/path/to/cmdproxy.exe".
> The result is that all externals programs made to be used with
> "cmdproxy.exe" are crashing Emacs.
> In the case of `helm', the user is crashing Emacs with the helm-locate
> command which use the executable "es.exe" which is part of "everything"
> program.
> So I think these crash are not the fault of Emacs nor helm, but a bad
> setting of user.
>
> So the question is:
> Sebastien, are you still using shell-file-name==bash in your config ?

The answer is yes:

  ╭────
  │ shell-file-name is a variable defined in `C source code'.
  │ Its value is "c:/cygwin/bin/bash.exe"
  ╰────

IIRC, I was asked by Eli (or, at the very least, allowed) to set back Bash as
my inferior shell.

FYI, I'm using that setting since 1999, when I began really working with
Emacs, and it did not cause any problems either with Helm (in that time,
Anything) for the last years in which I used it (at least, from 2010).

Problems began appearing with Emacs 24, IIRC.

That does not mean I absolutely have to keep that setting, but this is _by far_
my preferred one, as I'm using Cygwin Bash (or Zsh) all around the place, and
I want to be able to do the exact same thing from withing Emacs: for example,
calling one of my script on a selected region, or things like that.

Best regards,
  Seb

-- 
Sebastien Vauban

Message #17 received at 13701 <at> debbugs.gnu.org (full text, mbox):

From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
To: "Sebastien Vauban" <wxhgmqzgwmuf <at> spammotel.com>
Cc: 13701 <at> debbugs.gnu.org
Subject: Re: bug#13701: 24.2.93; Segmentation fault
Date: Wed, 13 Feb 2013 10:04:15 +0100

Hi Sébastien,

"Sebastien Vauban" <wxhgmqzgwmuf <at> spammotel.com> writes:

> Hi Thierry, Glenn and all,
>
> Thierry Volpiatto wrote:
>> Glenn Morris <rgm <at> gnu.org> writes:
>>> "Sebastien Vauban" wrote:
>>>
>>>> warning: sys_read called when read is in progress
>>>
>>> Searching for this message, I found that the only hit is crashes
>>> previously reported by you in Emacs 24.1 and 24.2:
>>>
>>> http://lists.gnu.org/archive/html/help-gnu-emacs/2012-10/msg00021.html
>>>
>>> So maybe the issue(s) is not new and is caused by some unusual
>>> circumstance on your machine.
>>
>> The initial problem was the user is setting `shell-file-name' to
>> "/path/to/bash" on a windows machine where the value is normally
>> "/path/to/cmdproxy.exe".
>> The result is that all externals programs made to be used with
>> "cmdproxy.exe" are crashing Emacs.
>> In the case of `helm', the user is crashing Emacs with the helm-locate
>> command which use the executable "es.exe" which is part of "everything"
>> program.
>> So I think these crash are not the fault of Emacs nor helm, but a bad
>> setting of user.
>>
>> So the question is:
>> Sebastien, are you still using shell-file-name==bash in your config ?
>
> The answer is yes:
>
>   ╭────
>   │ shell-file-name is a variable defined in `C source code'.
>   │ Its value is "c:/cygwin/bin/bash.exe"
>   ╰────
>
> IIRC, I was asked by Eli (or, at the very least, allowed) to set back Bash as
> my inferior shell.
>
> FYI, I'm using that setting since 1999, when I began really working with
> Emacs, and it did not cause any problems either with Helm (in that time,
> Anything) for the last years in which I used it (at least, from 2010).
At the beginning of anything, locate was not implemented for windows
with "everything", probably helm is working without crash if you use the
locate executable of your cygwin stuff instead of "everything".
So I repeat that helm itself is NOT crashing Emacs, but the backend used
by helm in an unsupported shell IS crashing Emacs.

> Problems began appearing with Emacs 24, IIRC.
This is not related to Emacs-24 IMO, same problem would happen in
Emacs-23 in same context.

> That does not mean I absolutely have to keep that setting, but this is _by far_
> my preferred one, as I'm using Cygwin Bash (or Zsh) all around the place, and
> I want to be able to do the exact same thing from withing Emacs: for example,
> calling one of my script on a selected region, or things like that.
Probably you should let-bind `shell-file-name' to "bash" or whatever
when calling your scripts from Emacs and leave the global value to its
default setting.

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.
(probably it is what Eli want to fix)

-- 
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

Message #20 received at 13701 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
Cc: wxhgmqzgwmuf <at> spammotel.com, 13701 <at> debbugs.gnu.org
Subject: Re: bug#13701: 24.2.93; Segmentation fault
Date: Wed, 13 Feb 2013 19:47:07 +0200

> From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
> Date: Wed, 13 Feb 2013 10:04:15 +0100
> Cc: 13701 <at> 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).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.