[gnutls-devel] GnuTLS | Automatically NULLify after gnutls_free() (!923)

[Development of GNU's TLS library]

>> We should also turn this off in the valgrind and address sanitizer CI runs, so that any memory errors are not masked by it.
> But maybe you have something in mind that I don't think of !?

I was thinking masking a double free such as:
```
gnutls_free(ptr);
/* do something */
gnutls_free(ptr);
```
But thinking it further, this is now a "logic" error with no repercussions whatsoever, and the fact that we eliminate explicit nullifications, makes such modification of the lib (without gnutls_free setting ptr to null) quite impossible to operate. So I no longer think this is a good idea.

> Regarding `CONTRIBUTION.md` I'd suggest a new section/paragraph with a short introduction to the basic GnuTLS memory functions. Is that OK ?

It makes sense to me.

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/merge_requests/923#note_141609187
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20190215/11a871a5/attachment.html>