From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23200 invoked by alias); 18 Apr 2014 14:56:25 -0000 Mailing-List: contact glibc-bugs-regex-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-regex-owner@sourceware.org Received: (qmail 23168 invoked by uid 48); 18 Apr 2014 14:56:22 -0000 From: "eggert at gnu dot org" To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/16851] re_node_set_alloc should not return REG_ESPACE when size == 0 Date: Fri, 18 Apr 2014 14:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: regex X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: std-isoc X-Bugzilla-Severity: normal X-Bugzilla-Who: eggert at gnu dot org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-04/txt/msg00003.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=16851 --- Comment #3 from Paul Eggert --- (In reply to Nathan Kennedy from comment #2) > re_node_set_alloc's use of malloc is not portable in that it needlessly > relies on current glibc malloc behavior not specified in any C standard Sure, but this is glibc. Glibc is allowed to rely on its own behavior, even if that behavior is not specified in the C standard. > such as in the two downstream projects (gnulib and uClibc). It's not a bug in gnulib, because of its use of MALLOC_0_IS_NONNULL. If there's a uClibc bug, they can fix it there. At some point, we may unify gnulib regex and glibc regex, and and that point we'll deal with this, but in the meantime there is no bug here. The simplest fix for the uClibc issue may be to modify uClibc so that its malloc is compatible with glibc. Yes, the C standard alllows uClibc's gratuitous incompability with glibc, but it's not good software engineering practice. But this is not the correct forum to discuss uClibc issues. -- You are receiving this mail because: You are on the CC list for the bug.