From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128231 invoked by alias); 24 Mar 2017 15:52:12 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 127844 invoked by uid 89); 24 Mar 2017 15:52:12 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=HTo:D*cx, Rich, preference, Hx-languages-length:574 X-HELO: mail-wm0-f48.google.com Received: from mail-wm0-f48.google.com (HELO mail-wm0-f48.google.com) (74.125.82.48) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 24 Mar 2017 15:52:11 +0000 Received: by mail-wm0-f48.google.com with SMTP id n11so5722095wma.0 for ; Fri, 24 Mar 2017 08:52:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=uxURzaAIUTN7K0N44kUjKl0dAgXK5OTpMWYHffNIQYE=; b=re8eaEAFdwB3+EvER91qHqVrWzFIAYiBH/PQOm7bJaGApuL5c6h6UzrLAzX3wlfN7y H12BJ1YZOygiW2+RoTeWXf2tPf0FennWn0+9CNOm8NFRdCmT1CIJrqc47WBcjX6feVfO Qh7irZn7/ZPN4x7BRXDCaeBagUXRWgRofOMVk29qUMoexYh7s6EgeT+IuXzqmWMw4jWl Ar8etbnfYTNQfNcL4Zvl5JkIM7CvS01WeyIjZJN3n7JdKbgQW0FTegQ8dt2lKhEPUpqk isk0VlTWsV3DL+De7BDaWviOY0P0JO5bGrxACak4v3P7a+6hlQuKMswfz44J547y8Btt /qwg== X-Gm-Message-State: AFeK/H1Cpm38Dq494TuYaF01oPseaSOdw9fm/gYHL6UVB3SoM5o3cu+CWmaQJFqjI2fwrjpB X-Received: by 10.28.159.73 with SMTP id i70mr3772821wme.78.1490370730177; Fri, 24 Mar 2017 08:52:10 -0700 (PDT) Received: from [192.168.0.101] ([37.189.166.198]) by smtp.gmail.com with ESMTPSA id l138sm2939450wmd.7.2017.03.24.08.52.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Mar 2017 08:52:09 -0700 (PDT) Subject: Re: [musl] Re: [PATCH] Fix invalid sigprocmask call To: Rich Felker , Yousong Zhou References: <1490324519-11228-1-git-send-email-yszhou4tech@gmail.com> <2b0bab84-e36e-e109-5444-dc84369dddce@redhat.com> <39f28782-65e8-0f52-3c8f-134a6f05788b@redhat.com> <20170324153530.GF17319@brightrain.aerifal.cx> Cc: gdb-patches@sourceware.org, musl@lists.openwall.com From: Pedro Alves Message-ID: <2db8b8b5-8145-19e2-238b-cf5e40108cba@redhat.com> Date: Fri, 24 Mar 2017 15:52:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20170324153530.GF17319@brightrain.aerifal.cx> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-03/txt/msg00447.txt.bz2 On 03/24/2017 03:35 PM, Rich Felker wrote: > If you file a report and it's deemed a bug in the standard and > changed, I'm happy to change this on the musl side. Just keep me > posted on what happens. Keep me posted as well. > I don't have any preference on what the > behavior "should" be here (IMO imposing a behavior when the caller has > violated constraints like passed a wrong value for how is pointless > anyway) but I do want to conform to the standard. IMO, no constrains were violated. Thanks, Pedro Alves