Re: Small fix: avoid passing null pointers to memcpy() - Mailing list pgsql-hackers

From Piotr Stefaniak
Subject Re: Small fix: avoid passing null pointers to memcpy()
Date
Msg-id BLU436-SMTP121BA7AAE8B0B6AA7D3E556F2690@phx.gbl
Whole thread Raw
In response to Small fix: avoid passing null pointers to memcpy()  (Piotr Stefaniak <postgres@piotr-stefaniak.me>)
Responses Re: Small fix: avoid passing null pointers to memcpy()  (Piotr Stefaniak <postgres@piotr-stefaniak.me>)
Re: Small fix: avoid passing null pointers to memcpy()  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2016-04-03 09:24, Piotr Stefaniak wrote:
> from running the regression test suite (including TAP tests) and also
> sqlsmith, I've got a couple of places where UBSan reported calls to
> memcpy() with null pointer passed as either source or destination.
>
> Patch attached.

Patch updated.

Since this time the patch includes fixes for other standard library
function calls (memset and bsearch), I'm renaming the patch file to be
more generic.


Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Detrimental performance impact of ringbuffers on performance
Next
From: Andreas Karlsson
Date:
Subject: Re: Refactor pg_dump as a library?