mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yousong Zhou <yszhou4tech@gmail.com>
Cc: gdb-patches@sourceware.org, musl@lists.openwall.com,
	Rich Felker <dalias@aerifal.cx>
Subject: Re: [PATCH] Fix invalid sigprocmask call
Date: Fri, 24 Mar 2017 13:37:21 +0000	[thread overview]
Message-ID: <306c1ba1-db66-f55f-3ab7-3b3eefd4564c@redhat.com> (raw)
In-Reply-To: <CAECwjAhpQMfz3vRWX=VFfJTBt+=950_fJnEj6H-6h05Vk85zjg@mail.gmail.com>

On 03/24/2017 01:05 PM, Yousong Zhou wrote:
> On 24 March 2017 at 20:55, Pedro Alves <palves@redhat.com> wrote:
>> The standard wasn't built on a vacuum.  It starts by ratifying common
>> implementation behavior.  If no historical implementation behaves like what
>> you're suggesting, what's the point of enforcing that, when it's clearly
>> NOT the intent?  You're just causing porting pain for no good reason.
>> Please file a bug against the standard to have the error section clarified instead.
> 
> Lol, now I will consider the idea of bumping the door of POSIX committee ;)

No need.  Go here:

 http://austingroupbugs.net/

> I am cc-ing musl-libc list now.

Original thread here:

 https://sourceware.org/ml/gdb-patches/2017-03/msg00426.html

Thanks,
Pedro Alves



  reply	other threads:[~2017-03-24 13:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1490324519-11228-1-git-send-email-yszhou4tech@gmail.com>
     [not found] ` <2b0bab84-e36e-e109-5444-dc84369dddce@redhat.com>
     [not found]   ` <CAECwjAgARveAhY=8e8J6Bcv+5=W=YnGcLY9G9Dv1sEnkNePVZA@mail.gmail.com>
     [not found]     ` <39f28782-65e8-0f52-3c8f-134a6f05788b@redhat.com>
2017-03-24 13:05       ` Yousong Zhou
2017-03-24 13:37         ` Pedro Alves [this message]
2017-03-25  0:35           ` Yousong Zhou
2017-03-24 15:35         ` [musl] " Rich Felker
2017-03-24 15:52           ` Pedro Alves
2017-03-24 16:41             ` Rich Felker
2017-03-24 17:33           ` Andreas Schwab
2017-03-24 18:14             ` Rich Felker

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=306c1ba1-db66-f55f-3ab7-3b3eefd4564c@redhat.com \
    --to=palves@redhat.com \
    --cc=dalias@aerifal.cx \
    --cc=gdb-patches@sourceware.org \
    --cc=musl@lists.openwall.com \
    --cc=yszhou4tech@gmail.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).