This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
RE: [PATCH] Check return from bfd_malloc
- From: msnyder at sonic dot net
- To: "Dave Korn" <dave dot korn at artimi dot com>
- Cc: msnyder at sonic dot net, binutils at sourceware dot org
- Date: Fri, 17 Aug 2007 12:35:35 -0700 (PDT)
- Subject: RE: [PATCH] Check return from bfd_malloc
- References: <12450.12.7.175.2.1185242096.squirrel@webmail.sonic.net> <20070724040320.GB27905@bubble.grove.modra.org> <16579.12.7.175.2.1185307145.squirrel@webmail.sonic.net> <021901c7ce40$b0fdf290$2e08a8c0@CAM.ARTIMI.COM>
> On 24 July 2007 20:59, msnyder@sonic.net wrote:
>
>>> On Mon, Jul 23, 2007 at 06:54:56PM -0700, msnyder@sonic.net wrote:
>>>> * opncls.c (bfd_make_writable): Check return from bfd_malloc
>>>> (Coverity).
>>>
>>> OK, but please don't advertise Coverity in the changelog entry.
>>
>> Agreed. Seems like they ought to get some recognition (they're
>> scanning open source code for free), but I'll confine it to
>> mention in the patch emails.
>
> I think it might be a nice tip of the hat to write a NEWS entry,
> mentioning
> that a series of security and reliability patches have been committed
> based on
> the information supplied by Coverity's auditing and thanking them for
> their
> contribution. Nothing crassly commercial, just credit where it's due. If
> you
> look at the gcc news page, you'll see it's perfectly accepted practice to
> credit both the organisation and the individuals who contribute a notable
> feature or enhancement.
OK, I am going to submit a NEWS blurb.
Thanks for the suggestion.