From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/11188 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.comp.gdb.patches,gmane.linux.lib.musl.general Subject: Re: [musl] Re: [PATCH] Fix invalid sigprocmask call Date: Fri, 24 Mar 2017 12:41:35 -0400 Message-ID: <20170324164135.GG17319@brightrain.aerifal.cx> 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> <2db8b8b5-8145-19e2-238b-cf5e40108cba@redhat.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1490373720 27697 195.159.176.226 (24 Mar 2017 16:42:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 24 Mar 2017 16:42:00 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Yousong Zhou , gdb-patches@sourceware.org, musl@lists.openwall.com To: Pedro Alves Original-X-From: gdb-patches-return-137805-gdb-gdb-patches=m.gmane.org@sourceware.org Fri Mar 24 17:41:56 2017 Return-path: Envelope-to: gdb-gdb-patches@m.gmane.org Original-Received: from server1.sourceware.org ([209.132.180.131] helo=sourceware.org) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1crSHV-0005d5-E6 for gdb-gdb-patches@m.gmane.org; Fri, 24 Mar 2017 17:41:41 +0100 DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=d4gs IU03nHMMwI3XxPnEd5lafAbR351xwxjItztKspP88e7anaCcHcZ9/mpHSPBq/Ohm PbpPHMjC9EuUjigJED5D88dH5NhK/5xvgD6wl/LZwLKg1YkLkwHNJOQ9AknvQgkG 5rCL4V7Qrbzah8w4GIhe7cwpaBD0rJDYsFoBNo4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:in-reply-to; s=default; bh=ALFhx8cHIA 46P2X+N1SYVHHjYRU=; b=WTyhw4DVaflPwUk/UIq4dc1t9hyyI49OTvb2SY2ILP Ek3KzbzxjsRzPDy9RWP/NSW+JYEaYYE43MKbejPgk8JR5OTR7xo3jtAuHeIHhwuq cAL5EQpa1y+3wHrxz43rf9ivNvgHQyscd9Ok8JWNIjOBa5Spq4sqWbueBZ1994iB 8= Original-Received: (qmail 63146 invoked by alias); 24 Mar 2017 16:41:42 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Original-Sender: gdb-patches-owner@sourceware.org Original-Received: (qmail 63135 invoked by uid 89); 24 Mar 2017 16:41:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-HELO: brightrain.aerifal.cx Original-Received: from 216-197-64-233.tingfiber.com (HELO brightrain.aerifal.cx) (216.197.64.233) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 24 Mar 2017 16:41:41 +0000 Original-Received: from dalias by brightrain.aerifal.cx with local (Exim 3.15 #2) id 1crSHP-0007BE-00; Fri, 24 Mar 2017 16:41:35 +0000 Content-Disposition: inline In-Reply-To: <2db8b8b5-8145-19e2-238b-cf5e40108cba@redhat.com> Xref: news.gmane.org gmane.comp.gdb.patches:122761 gmane.linux.lib.musl.general:11188 Archived-At: On Fri, Mar 24, 2017 at 03:52:08PM +0000, Pedro Alves wrote: > 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. I don't mean a constraint in the formal sense. Rather I'm talking about the whole class of errors that are "programming mistake caused a wrong/nonsensical value to be passed for an argument" as opposed to errors that can legitimately happen in a non-buggy program (out of memory, no such file, limit exceeded, invalid input, etc.). Sorry I wasn't clear. Rich