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, 13 insertions, 8 deletions

diff --git a/src/platform/windows/win_file.c b/src/platform/windows/win_file.c
index 3b6461a6..47bb87af 100644
--- a/src/platform/windows/win_file.c
+++ b/src/platform/windows/win_file.c
@@ -136,14 +136,19 @@ nni_plat_file_get(const char *name, void **datap, size_t *lenp)
 		rv = nni_win_error(GetLastError());
 		goto done;
 	}
-	if ((data = nni_alloc((size_t) sz)) == NULL) {
-		rv = NNG_ENOMEM;
-		goto done;
-	}
-	if (!ReadFile(h, data, sz, &nread, NULL)) {
-		rv = nni_win_error(GetLastError());
-		nni_free(data, sz);
-		goto done;
+	if (sz > 0) {
+		if ((data = nni_alloc((size_t) sz)) == NULL) {
+			rv = NNG_ENOMEM;
+			goto done;
+		}
+		if (!ReadFile(h, data, sz, &nread, NULL)) {
+			rv = nni_win_error(GetLastError());
+			nni_free(data, sz);
+			goto done;
+		}
+	} else {
+		data  = NULL;
+		nread = 0;
 	}
 
 	// We can get a short read, indicating end of file.  We return