|
From: | GNU bug Tracking System |
Subject: | bug#58096: closed (support malloc NULL return) |
Date: | Mon, 26 Sep 2022 18:09:02 +0000 |
Your message dated Mon, 26 Sep 2022 11:08:40 -0700 with message-id <987f3871-7c58-e4c9-d205-1609386d57c0@cs.ucla.edu> and subject line Re: bug#58096: support malloc NULL return has caused the debbugs.gnu.org bug report #58096, regarding support malloc NULL return to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 58096: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58096 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: support malloc NULL return Date: Mon, 26 Sep 2022 12:19:19 +0300 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!
--- End Message ---
--- Begin Message ---Subject: Re: bug#58096: support malloc NULL return Date: Mon, 26 Sep 2022 11:08:40 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 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
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |