public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yucong Sun <sunyucong@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Jemalloc under CYGWIN
Date: Fri, 16 Oct 2015 15:57:00 -0000	[thread overview]
Message-ID: <CAJygYd1tU+Nc5+owTw0Lfuk8SWQQS2vE1mhKjoz5br4c9zVF8A@mail.gmail.com> (raw)
In-Reply-To: <CAJygYd2T9JSJCDT178F8mzmuA79MsBbWCLsr8eF7Aguxk_-YWQ@mail.gmail.com>

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

  reply	other threads:[~2015-10-16 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 11:18 Yucong Sun
2015-10-16 15:57 ` Yucong Sun [this message]
2015-10-21 10:53   ` Corinna Vinschen
2015-10-21 13:50     ` Yucong Sun
2015-10-21 14:15       ` Yucong Sun
2015-10-21 14:16       ` Corinna Vinschen
2015-10-21 15:40         ` Yucong Sun
2015-10-21 16:06           ` Corinna Vinschen
2015-11-26  9:34             ` Corinna Vinschen
     [not found]               ` <CAJygYd232P=HQVufwQKtU37hHDiJZO5gzpM7fPKndLGMycJBgw@mail.gmail.com>
2015-12-05 14:32                 ` Yucong Sun
2015-12-05 17:05                   ` Andrey Repin
2015-12-06 14:08                   ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJygYd1tU+Nc5+owTw0Lfuk8SWQQS2vE1mhKjoz5br4c9zVF8A@mail.gmail.com \
    --to=sunyucong@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).