fixes #611 Memory Leaks under Windows

fixes #622 incorrect assumptions about malloc(0)

Windows actually allocates an object of size zero when calling
malloc on size zero.  This is unusual behavior, and we just
add logic to work more like malloc on POSIX systems.

Other systems can return non-NULL objects to fixed pages here.
We think the best option here is to uniformly return NULL from
our APIs in these circumstances, and to include testing to validate
that.

1 files changed, 2 insertions, 2 deletions

diff --git a/src/platform/posix/posix_alloc.c b/src/platform/posix/posix_alloc.c
index f4b0245c..f0847408 100644
--- a/src/platform/posix/posix_alloc.c
+++ b/src/platform/posix/posix_alloc.c
@@ -17,13 +17,13 @@
 void *
 nni_alloc(size_t sz)
 {
-	return (malloc(sz));
+	return (sz > 0 ? malloc(sz) : NULL);
 }
 
 void *
 nni_zalloc(size_t sz)
 {
-	return (calloc(1, sz));
+	return (sz > 0 ? calloc(1, sz) : NULL);
 }
 
 void