From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <cygwin-return-199523-listarch-cygwin=sourceware.org@cygwin.com>
Received: (qmail 97939 invoked by alias); 16 Oct 2015 15:57:07 -0000
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Received: (qmail 97366 invoked by uid 89); 16 Oct 2015 15:57:06 -0000
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
Received: from mail-oi0-f48.google.com (HELO mail-oi0-f48.google.com) (209.85.218.48) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 16 Oct 2015 15:57:05 +0000
Received: by oies66 with SMTP id s66so26889162oie.1        for <cygwin@cygwin.com>; Fri, 16 Oct 2015 08:57:03 -0700 (PDT)
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
Received: by 10.202.222.85 with HTTP; Fri, 16 Oct 2015 08:56:34 -0700 (PDT)
In-Reply-To: <CAJygYd2T9JSJCDT178F8mzmuA79MsBbWCLsr8eF7Aguxk_-YWQ@mail.gmail.com>
References: <CAJygYd2T9JSJCDT178F8mzmuA79MsBbWCLsr8eF7Aguxk_-YWQ@mail.gmail.com>
From: Yucong Sun <sunyucong@gmail.com>
Date: Fri, 16 Oct 2015 15:57:00 -0000
Message-ID: <CAJygYd1tU+Nc5+owTw0Lfuk8SWQQS2vE1mhKjoz5br4c9zVF8A@mail.gmail.com>
Subject: Re: Jemalloc under CYGWIN
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2015-10/txt/msg00232.txt.bz2

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@gmail.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