From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6334 Path: news.gmane.org!not-for-mail From: Samuel Holland Newsgroups: gmane.linux.lib.musl.general Subject: regcomp regression? Date: Wed, 15 Oct 2014 16:01:25 -0500 Message-ID: <543EE0A5.2000905@sholland.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1413406889 618 80.91.229.3 (15 Oct 2014 21:01:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Oct 2014 21:01:29 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6347-gllmg-musl=m.gmane.org@lists.openwall.com Wed Oct 15 23:01:25 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1XeVhE-0007X3-I4 for gllmg-musl@plane.gmane.org; Wed, 15 Oct 2014 23:01:24 +0200 Original-Received: (qmail 10098 invoked by uid 550); 15 Oct 2014 21:01:21 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 10080 invoked from network); 15 Oct 2014 21:01:20 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sholland.net; s=key1; t=1413406885; bh=vKpNA+/kFyg5GJo7rvfJkw6WaBEZPlYo5J2SZj/QDw4=; h=Date:From:To:Subject; b=cq7BCPLLaK5SzHX2PUyY0zDbs8Sz9IIJA+srDLy+KHt3YHSg4s4cLb2TOUa4xHR91 zYQ57a2xJr0g1KnQzrXo9PVJk+kPLOFuMkab3mV+fsr5kz4LSjDFsa67PsJ0gNXogU l/1LVBd2FBXs25cNvON+pkvQZ0+U8LT0AFQd+qjo= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 Xref: news.gmane.org gmane.linux.lib.musl.general:6334 Archived-At: Hello, I've been rebuilding packages after the 1.1.5 release, and it's caused some (apparent) regressions. file no longer compiles as it is unable to parse one of its magic files. The offending regex is (windows, line 163) \\`(\r\n|;|[[]|\xFF\xFE) It's testing for the BOM at the beginning of an INI/INF file. I understand the regex rewrite removed[1] the ability to match arbitrary bytes (even with the C locale) because it was broken; is this something you plan to add back? Or is the application wrong? If so, what workaround do you suggest? The m4 testsuite also now fails tests 109 and 121; this seems to be caused by the same change. [1] http://git.musl-libc.org/cgit/musl/commit?id=ec1aed0a144b3e00e16eeb142c9d13362d6048e7 -- Regards, Samuel Holland