From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.2 required=3.0 tests=AWL,BAYES_00, DATE_IN_PAST_24_48,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 88BD51F453 for ; Sun, 23 Sep 2018 08:01:39 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id BA23A120A14; Sun, 23 Sep 2018 17:01:37 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTPS id D68C01209EC for ; Sun, 23 Sep 2018 17:01:34 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 9E92E1F453; Sun, 23 Sep 2018 08:01:31 +0000 (UTC) Date: Fri, 21 Sep 2018 09:32:49 +0000 From: Eric Wong To: ruby-core@ruby-lang.org Message-ID: <20180921093249.GA76872@cinder> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-ML-Name: ruby-core X-Mail-Count: 89135 Subject: [ruby-core:89135] Re: [Ruby trunk Bug#14807] 2.6.0-preview2 segfaults on OpenBSD due to missing pthread_condattr_init call X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" > https://bugs.ruby-lang.org/issues/14807#change-74146 Right, already in trunk at r63548 And back to Jeremy's earlier comment: > It's defined but I don't think it would be usable: > > /usr/include/pthread.h:#define PTHREAD_COND_INITIALIZER NULL Without reading the OpenBSD pthreads library source code; I suspect that it would be usable. The condvar implementation can safely perform lazy-initialization because it can rely on the underlying mutex for protection.