From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 1215 invoked from network); 16 Dec 2021 11:22:55 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 16 Dec 2021 11:22:55 -0000 Received: (qmail 7240 invoked by uid 550); 16 Dec 2021 11:22:53 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 7205 invoked from network); 16 Dec 2021 11:22:52 -0000 Date: Thu, 16 Dec 2021 11:22:34 +0000 From: Ron Yorston To: musl@lists.openwall.com, arsnyder16@gmail.com Cc: quinq@fifth.space, musl@lists.openwall.com Message-ID: <61bb217a.wksjpcsr1v0gBuCq%rmy@frippery.org> References: <20211214160327.GA1494342@port70.net> <20211215190914.233d3021.quinq@fifth.space> <20211215212126.GK7074@brightrain.aerifal.cx> In-Reply-To: <20211215212126.GK7074@brightrain.aerifal.cx> User-Agent: Heirloom mailx 12.5 7/5/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BlackCat-Spam-Score: 9 Subject: Re: [musl] print does not support variable width plus padding Rich Felker wrote: >FWIW I suspect the problem is that Busybox is not recognizing the 0 >character as a flag (which it is, in the printf grammar) and thinks >it's the leading character of a width, making the * specifier for >width invalid (since a width was already seen). Quite so. 0 was missing from the list of valid flag characters. Moreover only one flag character was being processed so the format '%0 d', for example, was also considered invalid. I've submitted a patch to BusyBox. Ron