Greetings, Daniel Colascione!
>> [cmd /c start foo not going into the background]
>> It is not likely to change.
> What worries me isn't that the behavior changed, but that the new
> behavior is weird. SIGINT doesn't work on processes spawned by cmd /c
> start.
> Try it yourself:
> $ cmd /c sta
Hi,
Same here. Everything is working fine now.
Thanks a lot for the support.
Happy Cygwin,
Rob
>
> Thanks for the test case. This was due to Cygwin's not dealing well
> with Windows reuse of pids.
>
> It should be fixed in today's snapshot when it shows up at:
>
> http://cygwin.com/snapshots/
On 5/8/2012 5:11 PM, Christopher Faylor wrote:
Thanks for the test case. This was due to Cygwin's not dealing well with
Windows reuse of pids.
It should be fixed in today's snapshot when it shows up at:
http://cygwin.com/snapshots/
cgf
confirmed
Thanks
Marco
--
Pr
On Tue, May 08, 2012 at 01:50:21PM +0200, Rob Burgers wrote:
>Hi Christopher,
>
>I managed to create a simple replicator for the latest issue with the
>2012-05-07 snapshot.
>
>The script below crashes within seconds with the 'Resource temporarily
>unavailable' message.
>
>
>f.
On 5/8/2012 1:50 PM, Rob Burgers wrote:
Hi Christopher,
I managed to create a simple replicator for the latest issue with the
2012-05-07 snapshot.
The script below crashes within seconds with the 'Resource temporarily
unavailable' message.
f.sh:
#!/b
Hi Christopher,
I managed to create a simple replicator for the latest issue with the
2012-05-07 snapshot.
The script below crashes within seconds with the 'Resource temporarily
unavailable' message.
f.sh:
#!/bin/bash
cmd /C start notepad
while ( tru
Hi Christopher,
Thanks a lot for your concern and for the patch. Everything appeared to be okay
at first glance when applying it to the test applications.
However there might be some regression issue still: When I used it against our
application that originally triggered the issue I got error m
On Mon, May 07, 2012 at 11:15:42AM -0400, Christopher Faylor wrote:
>On Sun, May 06, 2012 at 04:09:51PM -0400, Christopher Faylor wrote:
>>On Sun, May 06, 2012 at 10:05:00PM +0200, Rob Burgers wrote:
>>>Corinna wrote:
If Cygwin behaves different than Linux then that's not really intended.
H
On Sun, May 06, 2012 at 04:09:51PM -0400, Christopher Faylor wrote:
>On Sun, May 06, 2012 at 10:05:00PM +0200, Rob Burgers wrote:
>>Corinna wrote:
>>>If Cygwin behaves different than Linux then that's not really intended.
>>>However, this only goes as far as Cygwin processes are affected. We
>>>ca
On 5/6/12 1:09 PM, Christopher Faylor wrote:
> [cmd /c start foo not going into the background]
> It is not likely to change.
What worries me isn't that the behavior changed, but that the new
behavior is weird. SIGINT doesn't work on processes spawned by cmd /c
start.
Try it yourself:
$ cmd /c s
On Sun, May 06, 2012 at 10:05:00PM +0200, Rob Burgers wrote:
>Corinna wrote:
>>If Cygwin behaves different than Linux then that's not really intended.
>>However, this only goes as far as Cygwin processes are affected. We
>>can't (and don't) make any such guarantee for native, non-Cygwin
>>processe
Hi Corinna,
Thanks for your answer.
> If Cygwin behaves different than Linux then that's not really intended.
> However, this only goes as far as Cygwin processes are affected. We can't
> (and don't) make any such guarantee for native, non-Cygwin processes.
Okay, may be we should review our sta
On May 5 10:05, Rob Burgers wrote:
> Hi,
>
> The issue I'm raising in here may be related to this post:
> http://cygwin.com/ml/cygwin/2012-05/msg00081.html
> It is the first time I read that something may have changed in this area.
> This is to me unexpected and it caused us quite some debuggin
Hi,
The issue I'm raising in here may be related to this post:
http://cygwin.com/ml/cygwin/2012-05/msg00081.html
It is the first time I read that something may have changed in this area. This
is to me unexpected and it caused us quite some debugging to find out as the
relation between the updat
On Fri, May 4, 2012 at 3:19 AM, Rob Burgers wrote:
> Hi,
>
> I am having trouble with a not returning command prompt after termination of
> a process when this process forked another process. In such case the return
> of the command prompt is bound to life time of the forked process i.e. when
>
15 matches
Mail list logo
