Re: fork problem on latest cygwin CVS

2011-11-16 Thread Christopher Faylor
On Wed, Nov 16, 2011 at 11:01:16PM +0100, marco atzeri wrote: >On 11/16/2011 8:14 PM, Christopher Faylor wrote: >> On Tue, Nov 15, 2011 at 02:22:02PM -0500, Christopher Faylor wrote: >>> On Tue, Nov 15, 2011 at 04:04:16PM +0100, marco atzeri wrote: On 11/14/2011 6:11 PM, Christopher Faylor wro

Re: fork problem on latest cygwin CVS

2011-11-16 Thread marco atzeri
On 11/16/2011 8:14 PM, Christopher Faylor wrote: On Tue, Nov 15, 2011 at 02:22:02PM -0500, Christopher Faylor wrote: On Tue, Nov 15, 2011 at 04:04:16PM +0100, marco atzeri wrote: On 11/14/2011 6:11 PM, Christopher Faylor wrote: FYI, the last thing any developer wants to hear after a major cod

Re: fork problem on latest cygwin CVS

2011-11-16 Thread Christopher Faylor
On Tue, Nov 15, 2011 at 02:22:02PM -0500, Christopher Faylor wrote: >On Tue, Nov 15, 2011 at 04:04:16PM +0100, marco atzeri wrote: >>On 11/14/2011 6:11 PM, Christopher Faylor wrote: >> >>> FYI, the last thing any developer wants to hear after a major code >>> change is a generic "It's broke" report

Re: fork problem on latest cygwin CVS

2011-11-15 Thread Christopher Faylor
On Tue, Nov 15, 2011 at 04:04:16PM +0100, marco atzeri wrote: >On 11/14/2011 6:11 PM, Christopher Faylor wrote: > >> FYI, the last thing any developer wants to hear after a major code >> change is a generic "It's broke" report with no details and no way to >> duplicate the problem. A stack trace f

Re: fork problem on latest cygwin CVS

2011-11-15 Thread marco atzeri
On 11/14/2011 6:11 PM, Christopher Faylor wrote: FYI, the last thing any developer wants to hear after a major code change is a generic "It's broke" report with no details and no way to duplicate the problem. A stack trace from a home-grown version of cygwin1.dll is not a detail. It's meaningl

Re: fork problem on latest cygwin CVS

2011-11-14 Thread Christopher Faylor
On Mon, Nov 14, 2011 at 05:09:07PM +0100, marco atzeri wrote: >On 11/14/2011 4:31 PM, Christopher Faylor wrote: >> On Mon, Nov 14, 2011 at 03:40:32PM +0100, marco atzeri wrote: >>> Hi Cgf, >>> >>> >>> after updating cygwin CVS build from >>>http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00063.html

Re: fork problem on latest cygwin CVS

2011-11-14 Thread marco atzeri
On 11/14/2011 4:31 PM, Christopher Faylor wrote: On Mon, Nov 14, 2011 at 03:40:32PM +0100, marco atzeri wrote: Hi Cgf, after updating cygwin CVS build from http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00063.html to http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00064.html .. 66html on CYGWIN_

Re: fork problem on latest cygwin CVS

2011-11-14 Thread Christopher Faylor
On Mon, Nov 14, 2011 at 03:40:32PM +0100, marco atzeri wrote: >Hi Cgf, > > >after updating cygwin CVS build from > http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00063.html >to > http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00064.html .. 66html > >on CYGWIN_NT-6.1-WOW64 > >the shell have fork issues

fork problem on latest cygwin CVS

2011-11-14 Thread marco atzeri
Hi Cgf, after updating cygwin CVS build from http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00063.html to http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00064.html .. 66html on CYGWIN_NT-6.1-WOW64 the shell have fork issues during make/build session. 1 [main] sh 6768 E:\cygwin\bin\sh.exe: