> What exactly is the malloc problem you're seeing? The specific problem I'm having is that jemalloc's malloc_init() calls needs to use pthread_mutex_init() or even pthread_mutex with a initializer. Both in-turn uses malloc, triggering this issue.
A quick fix would be somehow make pthread always use system malloc/free, which shouldn't be that bad. Another issue I saw is that jemalloc will use readlink() for "/etc/jemalloc.conf" during malloc_init(), which on cygwin, this function uses "new" to do some path manipulating work, which also have the same issue. However, we can probably just disable that . So, the quickest fix would be to make cygwin's thread implementations always use system malloc. some small workarounds in jemalloc would be needed afterwards, but it should be a nice starting point. -- 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
