[PATCH] Fix calling memchr or memcpy with NULL pointer

BC
b17 c0de
Sun, Oct 9, 2016 8:17 AM

Hi,
Calling memchr() or memcpy() with NULL pointer arguments is always
undefined behavior (even if the length argument is also 0). Please
apply.

Kal

Hi, Calling memchr() or memcpy() with NULL pointer arguments is always undefined behavior (even if the length argument is also 0). Please apply. Kal
NI
Nanang Izzuddin
Mon, Oct 24, 2016 3:25 AM

Hi Kal,

Just checked in the patch to SVN trunk at
https://trac.pjsip.org/repos/changeset/5468.

Thank you for the patch.

BR,
nanang

On Sun, Oct 9, 2016 at 3:17 PM, b17 c0de b17c0de@gmail.com wrote:

Hi,
Calling memchr() or memcpy() with NULL pointer arguments is always
undefined behavior (even if the length argument is also 0). Please
apply.

Kal


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

Hi Kal, Just checked in the patch to SVN trunk at https://trac.pjsip.org/repos/changeset/5468. Thank you for the patch. BR, nanang On Sun, Oct 9, 2016 at 3:17 PM, b17 c0de <b17c0de@gmail.com> wrote: > Hi, > Calling memchr() or memcpy() with NULL pointer arguments is always > undefined behavior (even if the length argument is also 0). Please > apply. > > Kal > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >