X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=RqwMQP7
	JuI17NgMm/Rx0dcWmpIb8FTmcpMAx3kJgN8mkqd/Qpix/py0Rg9hYWEyq9WJ1pMe
	QqmeAvJDTNhLe88nD75NBRlADjb1kzkYsqEPGgjsN4xkZ7FH3J6M3058y5duDJ1h
	IHtnt0YbgMuDx1KpOnRo/+LXuUAhAhXWcIa4=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=ccRvzEhIGP5k7
	25JIv+8Zs1gWYk=; b=UOQOzZe8UaBxXkYz1SU0fpGYTj2zya9x1umZWR6L2uv6p
	aR81LwbXYom0oVmyopqsS4mneeob0FO1ilmBwJ5V9wDozy7WZGpoOv2tp0ZvrCLO
	EERBVkAcpWtMBrBQ6dnOPHkMcSlEnQM9oQrtdL4lD4azHRqv0/hJldTeHcFtE4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-oi0-f48.google.com
X-Received:	by 10.202.90.84 with SMTP id o81mr9657584oib.38.1445011023700; Fri, 16 Oct 2015 08:57:03 -0700 (PDT)
MIME-Version:	1.0
In-Reply-To:	<CAJygYd2T9JSJCDT178F8mzmuA79MsBbWCLsr8eF7Aguxk_-YWQ@mail.gmail.com>
References:	<CAJygYd2T9JSJCDT178F8mzmuA79MsBbWCLsr8eF7Aguxk_-YWQ AT mail DOT gmail DOT com>
From:	Yucong Sun <sunyucong AT gmail DOT com>
Date:	Fri, 16 Oct 2015 23:56:34 +0800
Message-ID:	<CAJygYd1tU+Nc5+owTw0Lfuk8SWQQS2vE1mhKjoz5br4c9zVF8A@mail.gmail.com>
Subject:	Re: Jemalloc under CYGWIN
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

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 workaround this issue?

On Wed, Oct 7, 2015 at 7:17 PM, Yucong Sun <sunyucong AT gmail DOT com> wrote:
> 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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -