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 >>> 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. >> >> Come on, you know the drill by now. How about a simple test case? > >I know the drill, but I just updated from XP-32 to W7-64, >one disk crashed, so I am reinstalling everything from scratch and >taking a test case when building octave is never easy. > >So I need time to give you a simple test case, and eventually >someone else will notice the same problem in advance. > >FYI 2011-11-08 snapshot does not suffer such problem.
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 meaningless unless the addresses are decoded. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
