GNU bug report logs - #58096
support malloc NULL return

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 58096 in the body.
You can then email your comments to 58096 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Aleksandar Kostadinov <akostadinov <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: support malloc NULL return
Date: Mon, 26 Sep 2022 12:19:19 +0300

[Message part 1 (text/plain, inline)]

Hello,

grep fails when using a certain malloc implementation (memkind) because of
its reliance on malloc returning 0 when zero size is passed to it. Memkind
returns NULL instead which according to authors [1] is one of the
acceptable values in malloc specification.

Can grep be updated to also support a NULL return value?

Thank you!

[1] https://github.com/memkind/memkind/issues/853#issuecomment-1241678167

[Message part 2 (text/html, inline)]

Message #10 received at 58096-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Aleksandar Kostadinov <akostadinov <at> gmail.com>
Cc: 58096-done <at> debbugs.gnu.org
Subject: Re: bug#58096: support malloc NULL return
Date: Mon, 26 Sep 2022 11:08:40 -0700

On 9/26/22 02:19, Aleksandar Kostadinov wrote:
> Can grep be updated to also support a NULL return value?

No need for an update, as grep has done that for many years.

This is a configuration problem on the part of the memkind user. See:

https://github.com/memkind/memkind/issues/853#issuecomment-1258417795

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.