On Dec 5 22:32, Yucong Sun wrote:
> I'm sorry, I got distracted from this issue and hadn't make any progress.
No worries.
> One thing specifically I need to be able to work on this issue is some
> information describing how to build/test cygwin lib (rather than using
> it). I couldn't find any i
Greetings, Yucong Sun!
> I'm sorry, I got distracted from this issue and hadn't make any progress.
> One thing specifically I need to be able to work on this issue is some
> information describing how to build/test cygwin lib (rather than using
> it). I couldn't find any information on the websit
I'm sorry, I got distracted from this issue and hadn't make any progress.
One thing specifically I need to be able to work on this issue is some
information describing how to build/test cygwin lib (rather than using
it). I couldn't find any information on the website, (or I havn't look
deeply enou
Hi Yucong Sun,
On Oct 21 17:40, Corinna Vinschen wrote:
> On Oct 21 22:43, Yucong Sun wrote:
> > On Wed, Oct 21, 2015 at 10:15 PM, Corinna Vinschen
> > wrote:
> > > On Oct 21 21:49, Yucong Sun wrote:
> > >> > What exactly is the malloc problem you're seeing?
> > >>
> > >> The specific problem I'm
On Oct 21 22:43, Yucong Sun wrote:
> On Wed, Oct 21, 2015 at 10:15 PM, Corinna Vinschen
> wrote:
> > 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 pthrea
On Wed, Oct 21, 2015 at 10:15 PM, Corinna Vinschen
wrote:
> 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
>> i
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.
>
> 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 alwa
On Oct 16 23:56, Yucong Sun wrote:
> Hi,
>
> Throught some frustrating and furious debugging I now understand the
> core issue here. CYGWIN calls malloc provided by jemalloc during
> initializations, which in turn calls pthreads functions, which in
> turn uses malloc, which also uses pthreads, c
Hi,
Throught some frustrating and furious debugging I now understand the
core issue here. CYGWIN calls malloc provided by jemalloc during
initializations, which in turn calls pthreads functions, which in
turn uses malloc, which also uses pthreads, causing a deadlock.
Now, is there anyway to wo
Hi there,
I'm trying to make jemalloc work with CYGWIN. and I've been meeting
with a mysterious deadlock issue on startup (from CYGWIN's
malloc-wrapper to jemalloc and pthread_mutex_lock get deadlock).
Has anyone else tried this?
Thanks
--
Problem reports: http://cygwin.com/problems.html
11 matches
Mail list logo