Tarantool development patches archive
 help / color / mirror / Atom feed
From: lvasiliev <lvasiliev@tarantool.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] Add a check whether glibc is used
Date: Wed, 22 Apr 2020 17:52:18 +0300	[thread overview]
Message-ID: <1ba0a66e-e252-99d7-5eb9-b5d5fbe8f95e@tarantool.org> (raw)
In-Reply-To: <20200422142046.GA3072@uranus>

Hi!

On 22.04.2020 17:20, Cyrill Gorcunov wrote:
> On Tue, Apr 21, 2020 at 08:44:57PM +0300, Leonid Vasiliev wrote:
>> The cbus hang test uses glibc pthread mutex implementation details.
>> Therefore, it should not compile in case of using another library.
>> ---
>> Now the compilation for alpine 3.5 is broken.
> 
> Wait, I don't understand. We'are using tt_pthread in core code
> as well. How tarantool compiles on it then?
The cbus hang test uses glibc pthread mutex implementation details
(internal fields of mutex).
Comment from code of cbus_hang test:
" We want to cancel canceled thread in the moment of cpipe_flush_cb
  will be processing.
  A Linux specific dirty hack will be used for reproduce the bug.
  We need to synchronize the main thread and the canceled worker thread.
  So, do it using the endpoint's mutex internal field(__data.__lock)."
"A Linux specific" - a glibc specific.

> 

  reply	other threads:[~2020-04-22 14:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 17:44 Leonid Vasiliev
2020-04-22 14:20 ` Cyrill Gorcunov
2020-04-22 14:52   ` lvasiliev [this message]
2020-04-22 15:36     ` Cyrill Gorcunov
2020-04-23  9:10       ` lvasiliev
2020-04-23  9:26         ` Cyrill Gorcunov
2020-04-23 10:52 ` Alexander Turenko
2020-04-23 11:37   ` lvasiliev
2020-04-24  7:24 ` Kirill Yukhin
2020-04-24  8:02   ` Kirill Yukhin
2020-04-25  6:43   ` Alexander Turenko

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=1ba0a66e-e252-99d7-5eb9-b5d5fbe8f95e@tarantool.org \
    --to=lvasiliev@tarantool.org \
    --cc=gorcunov@gmail.com \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] Add a check whether glibc is used' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox