Christopher Faylor wrote:
> Actually, this kind of error is more likely to be caused by a thread
> starting prior to cygwin initialization and grabbing cygwin's heap area
> to use for its stack.
Oh, of course! 2 meg of allocation is going to throw everything waaaay off!
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
