This is the mail archive of the
mailing list for the Cygwin project.
Re: Jemalloc under CYGWIN
- From: Yucong Sun <sunyucong at gmail dot com>
- To: cygwin at cygwin dot com, cygwin-developers at cygwin dot com
- Date: Wed, 21 Oct 2015 22:43:55 +0800
- Subject: Re: Jemalloc under CYGWIN
- Authentication-results: sourceware.org; auth=none
- References: <CAJygYd2T9JSJCDT178F8mzmuA79MsBbWCLsr8eF7Aguxk_-YWQ at mail dot gmail dot com> <CAJygYd1tU+Nc5+owTw0Lfuk8SWQQS2vE1mhKjoz5br4c9zVF8A at mail dot gmail dot com> <20151021105300 dot GN5319 at calimero dot vinschen dot de> <CAJygYd3o5tjmLx8e8zCFi+T5LxzBLk02nMrcC03Fp-MbnuBsHQ at mail dot gmail dot com> <20151021141523 dot GV5319 at calimero dot vinschen dot de>
On Wed, Oct 21, 2015 at 10:15 PM, Corinna Vinschen
> On Oct 21 21:49, Yucong Sun wrote:
>> > 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.
> What about using a native critical section instead? It shouldn't be too
> tricky to conditionalize this in jemalloc.
Possibly, jemalloc already have support of this. However I wasn't so
sure that this was possible before,
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple