in reply to Re^2: [Win32] pthreads and memory allocation
in thread [Win32] pthreads and memory allocation

I think that the problem is likely that malloc has been redefined by the Perl/XS headers and the Perl code that gets called is trying to access the perl thread context for the "current" thread. Which of course doesn't exist because the thread was not created by Perl.

See Re: Win32::Internet crash, XS, callbacks, perl stack & context, windows api, interpreter thread safety, 1 perl, many C threads by windows for previous related discussion on the problem.

See also Perl crash during perl_clone for a long and twisty thread where I worked through the same problem to a successful conclusion.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
  • Comment on Re^3: [Win32] pthreads and memory allocation

In Section Seekers of Perl Wisdom