From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14273 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: gettext API question - null pointer issue again Date: Thu, 27 Jun 2019 00:18:20 -0400 Message-ID: <20190627041820.GA29896@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="159961"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) Cc: musl@lists.openwall.com To: Bruno Haible Original-X-From: musl-return-14289-gllmg-musl=m.gmane.org@lists.openwall.com Thu Jun 27 06:18:38 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hgLrp-000fWq-SY for gllmg-musl@m.gmane.org; Thu, 27 Jun 2019 06:18:37 +0200 Original-Received: (qmail 15500 invoked by uid 550); 27 Jun 2019 04:18:35 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 15466 invoked from network); 27 Jun 2019 04:18:34 -0000 Content-Disposition: inline Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:14273 Archived-At: Could you answer a question about the gettext API that's come up again in the context of musl's implementation? The gettext manual documents that for the message key argument to these functions: "If the argument is NULL the result is undefined." https://www.gnu.org/software/gettext/manual/html_node/Interface-to-gettext.html And it looks like you've treated passing a null argument as a bug in the past: https://www.mail-archive.com/bug-gnulib@gnu.org/msg36249.html It's come up again with GIMP doing it: https://github.com/void-linux/void-packages/issues/12042 Should we continue to treat this as an application bug and ask the app maintainers to fix it when it's found? That's my leaning but I want to make sure we're still on the same page. Rich