This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Nope, didn't help; in fact, the rebase at 0x77000000 (whatever the recommendation was) broke things much worse; and now even bash won't start without a million access violations.
Why is this even necessary anyways? Other than "because it's always been this way"? I've been as stalwart a defender of cygwin as you'd find at my various companies over the years but this wart is getting really hard to ignore. In particular, since I myself can't do subversion or various other things any more without devolving to something like (ugh) tortoise.
Short answer: It's an artifact of emulating fork on Windows. Long answer: See the email archives for all the discussions about it and attempts to make this less painful.
-- Larry
A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email?
-- 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |