Yes, this makes the trick. After changing source code to#include <pthread.h> #include "EXTERN.h" #include "perl.h" #include "XSUB.h" #include "ppport.h" #undef free #undef malloc
You'll get away with that as long as you do not attempt to pass anything you malloc() to perl.
When it gets interesting is when you try to free() something allocated by Perl within your C/XS code; or vice versa.
As I mentioned above, under iThreads, different pools of memory are used for each (perl instantiated) thread via the custom allocator.
Attempt free something allocated by the CRT (ie. by you in your XS code with #undef malloc) and then free it using the custom allocators free() (eg. by passing it into Perl and then letting it go out of scope) and you'll probably get the infamous: "free to wrong pool" message.
Attempt to free something allocated by that allocator using the CRT free() and you'll blow up bigtime.
In reply to Re^9: XS: free() outside of the main thread causes crash on Windows
by BrowserUk
in thread XS: free() outside of the main thread causes crash on Windows
by OlegG
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |