RE: Failure with fork()

bably some > different problem, which still need investigating. At a glance, http://bugs.winehq.org/show_bug.cgi?id=24018#c9 describes a seemingly plausible etiology involving the dcrt0.cc code and differing stack-allocation semantics between wine and windows. -gmt -- Problem reports:

RE: Failure with fork()

I had to, I'd guess that once one fixes this new-but-maybe-old bug, another new-but-maybe-old bug is exposed, and once one fixes that, another, and so on, for "a while yet" before cygwin works "like a champ" in wine... the good news is, both projects are open source, so a

RE: Failure with fork()

ly an anticlimax where you simply find the next bug -- but one of the above would probably allow you to proceed; worst-case you'd at least have a build environment, for future testing/hacking, that you could recycle. -gmt -- 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

RE: UNC and POSIX paths

obably too late now. Although I hate to continue casting myself in this "advocate" role -- I really have very little stake in this -- otherwise you would have patches for this, rather than 1000 words. -gmt -- 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

RE: UNC and POSIX paths

n't think of one technical or merit-based reason this shouldn't be done, aside from the fact that it's annoying to hear it endlessly brought up on the mailing list (a problem which an implementation would, in fact, solve, not exacerbate). -gmt -- Problem reports: http://cygw

RE: UNC and POSIX paths

fix the upstreams committing these atrocities, it's the obvious reason -- occasionally one encounters a large body of dense, non-fixable-by-sed/perl, poorly commented "spaghetti" script-code that makes "clever," deep usage of the assumption that "//" == "/&qu

RE: UNC and POSIX paths

d to build while using the proposed anti-feature-feature (the inevitable response being, "shouldn't those packages just fix their broken configure scripts"? :P) -gmt -- 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

RE: pty issue causes 'screen' to hang when run from mintty as detached

ole! ;-) > > But seriously, it's just something different that doesn't conform to the > definition of a PTY. Windows doesn't have PTYs. It uses the console instead. So, no win32-console-specific fhandler exists, and clones of the win32 stdio handles are simply passed through cygwin