From: Ken Brown <kbrown@cornell.edu>
To: cygwin <cygwin@cygwin.com>
Subject: timerfd deadlock
Date: Fri, 07 Jun 2019 12:10:00 -0000 [thread overview]
Message-ID: <17657e77-6d7c-7367-3e6f-54e2586ed40c@cornell.edu> (raw)
While testing some new pipe code, I'm occasionally seeing a timerfd deadlock:
The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting for
the timerfd thread to close; and the timerfd thread is stuck at timerfd.cc:140,
waiting to acquire a mutex that's held by timerfd_tracker::dtor.
I see this maybe 1 out of 4 times that I run 'make -j13' on a clean emacs source
tree, and I see it only when my new pipe code is installed. So I don't know if
this is a bug in my code or if it's just coincidence that my code happens to
trigger a timerfd bug.
Ken
--
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
next reply other threads:[~2019-06-07 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 12:10 Ken Brown [this message]
2019-06-11 8:52 ` Corinna Vinschen
2019-06-11 13:18 ` Ken Brown
2019-06-24 20:16 ` Ken Brown
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=17657e77-6d7c-7367-3e6f-54e2586ed40c@cornell.edu \
--to=kbrown@cornell.edu \
--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).