Re: Cygwin Subprocesses on XEmacs

2015-01-30 Thread Dr. Volker Zell
> Vin Shelton writes: > I don't see this segfault. I am running the default version of gcc, > and I assume you are, too. Perhaps you need to rebaseall? I'm using the latest gcc-4.9.2 > Your build path is "...xemacs-21.4.22..." are you sure you're using > 21.4.23 sources

Re: Cygwin Subprocesses on XEmacs

2015-01-30 Thread Vin Shelton
Volker - On Fri, Jan 30, 2015 at 10:51 AM, Dr. Volker Zell wrote: > I downloaded the latest version 21.4.23 and tried to build it, but I > consistently get: > > gcc -c -ggdb -O2 -pipe -Wimplicit-function-declaration > -fdebug-prefix-map=/cygdrive/d/misc/src/release/xemacs-21.4.22-2.i686/build=/us

Re: Cygwin Subprocesses on XEmacs

2015-01-30 Thread Dr. Volker Zell
> Vin Shelton writes: > On Thu, Jan 29, 2015 at 4:39 AM, Corinna Vinschen wrote: >> On Jan 28 22:32, Vin Shelton wrote: >>> I think I have verified this behavior - I restored the old sysdep.c >>> module and moved the disconnect_controlling_terminal() call [which >>> calls s

Re: Cygwin Subprocesses on XEmacs

2015-01-29 Thread Corinna Vinschen
On Jan 29 06:49, Vin Shelton wrote: > On Thu, Jan 29, 2015 at 4:39 AM, Corinna Vinschen wrote: > > On Jan 28 22:32, Vin Shelton wrote: > >> I think I have verified this behavior - I restored the old sysdep.c > >> module and moved the disconnect_controlling_terminal() call [which > >> calls setsid()

Re: Cygwin Subprocesses on XEmacs

2015-01-29 Thread Vin Shelton
On Thu, Jan 29, 2015 at 4:39 AM, Corinna Vinschen wrote: > On Jan 28 22:32, Vin Shelton wrote: >> I think I have verified this behavior - I restored the old sysdep.c >> module and moved the disconnect_controlling_terminal() call [which >> calls setsid()] from right after the fork() to just before t

Re: Cygwin Subprocesses on XEmacs

2015-01-29 Thread Corinna Vinschen
Hi Vin, On Jan 28 22:32, Vin Shelton wrote: > Dear Corinna, et al - > > On Wed, Jan 28, 2015 at 8:58 AM, Corinna Vinschen wrote: > > On Jan 28 08:20, Vin Shelton wrote: > >> On Wed, Jan 28, 2015 at 4:53 AM, Corinna Vinschen wrote: > >> > On Jan 27 23:05, Vin Shelton wrote: > >> >> I spent some ti

Re: Cygwin Subprocesses on XEmacs

2015-01-28 Thread Vin Shelton
Dear Corinna, et al - On Wed, Jan 28, 2015 at 8:58 AM, Corinna Vinschen wrote: > On Jan 28 08:20, Vin Shelton wrote: >> On Wed, Jan 28, 2015 at 4:53 AM, Corinna Vinschen wrote: >> > On Jan 27 23:05, Vin Shelton wrote: >> >> I spent some time debugging M-x shell in XEmacs on 32-bit Cygwin. >> >> He

Re: Cygwin Subprocesses on XEmacs

2015-01-28 Thread Corinna Vinschen
On Jan 28 08:20, Vin Shelton wrote: > Hi, Corinna et al, > > On Wed, Jan 28, 2015 at 4:53 AM, Corinna Vinschen wrote: > > On Jan 27 23:05, Vin Shelton wrote: > >> I spent some time debugging M-x shell in XEmacs on 32-bit Cygwin. > >> Here's what I found out. > >> > >> In the child after fork() but

Re: Cygwin Subprocesses on XEmacs

2015-01-28 Thread Vin Shelton
Hi, Corinna et al, On Wed, Jan 28, 2015 at 4:53 AM, Corinna Vinschen wrote: > On Jan 27 23:05, Vin Shelton wrote: >> I spent some time debugging M-x shell in XEmacs on 32-bit Cygwin. >> Here's what I found out. >> >> In the child after fork() but before exec(), the setsid() call in >> disconnect_c

Re: Cygwin Subprocesses on XEmacs

2015-01-28 Thread Corinna Vinschen
Hi Vin, first of all, I haven't looked into the affected piece of code in Cygwin for a long time, and it was never my domain, so bear with me. On Jan 27 23:05, Vin Shelton wrote: > I spent some time debugging M-x shell in XEmacs on 32-bit Cygwin. > Here's what I found out. > > In the child aft

Cygwin Subprocesses on XEmacs

2015-01-27 Thread Vin Shelton
I spent some time debugging M-x shell in XEmacs on 32-bit Cygwin. Here's what I found out. In the child after fork() but before exec(), the setsid() call in disconnect_controlling_terminal() is causing the subprocess not to function after it gets spawned. Here is a patch which works around the pr