More debug goodies:

WINDOWS CRASH EMULATION!

If you use the -d (debug) argument for starting blender, it will now:

- set all freed memory to 0xFFFFFFFF
- set all malloced memory to 0xFFFFFFFF

The first option will give nice crashers when you read from freed memory.
The second option is for OSX especially, it has the nasty habit to give
zeroed mallocs.

1 files changed, 4 insertions, 0 deletions

diff --git a/intern/guardedalloc/MEM_guardedalloc.h b/intern/guardedalloc/MEM_guardedalloc.h
index ce9f2a273bd..26a9258d03b 100644
--- a/intern/guardedalloc/MEM_guardedalloc.h
+++ b/intern/guardedalloc/MEM_guardedalloc.h
@@ -115,6 +115,10 @@ extern "C" {
 	/** Set thread locking functions for safe memory allocation from multiple
 	    threads, pass NULL pointers to disable thread locking again. */
 	void MEM_set_lock_callback(void (*lock)(void), void (*unlock)(void));
+	
+	/** Attempt to enforce OSX (or other OS's) to have malloc and stack nonzero */
+	void MEM_set_memory_debug(void);
+
 
 #ifdef __cplusplus
 }