mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Rich Felker <dalias@aerifal.cx>, Yousong Zhou <yszhou4tech@gmail.com>
Cc: gdb-patches@sourceware.org, musl@lists.openwall.com
Subject: Re: [musl] Re: [PATCH] Fix invalid sigprocmask call
Date: Fri, 24 Mar 2017 15:52:08 +0000	[thread overview]
Message-ID: <2db8b8b5-8145-19e2-238b-cf5e40108cba@redhat.com> (raw)
In-Reply-To: <20170324153530.GF17319@brightrain.aerifal.cx>

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



  reply	other threads:[~2017-03-24 15:52 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
2017-03-25  0:35           ` Yousong Zhou
2017-03-24 15:35         ` [musl] " Rich Felker
2017-03-24 15:52           ` Pedro Alves [this message]
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=2db8b8b5-8145-19e2-238b-cf5e40108cba@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).