Re^3: Garbage collection problem?? (Win32 CRTL malloc)

Actually, it appears to be more to do with realloc and/or free rather than malloc per se, but also there seem to be some pretty strange things going on with respect to error handling.

I get the impression, but haven't got proof yet, that it may be something to do with the way Perl is using the CRT, possibly to do with how it handles errors.

Has anyone tried the OP code on a non-threaded 5.8.x Win32 build? There are lots ( literally millions) of repetitions of the call sequence:

...
[T1868] GetLastError(2845dc, 18f5ca4, 77c35292, 2803000e, ...) = 3
[T1868] TlsGetValue(0, 2845dc, 18f5ca4, 77c35292, ...) = 281ea0
[T1868] SetLastError(3, 2845dc, 18f5ca4, 77c35292, ...) = 7ffde000
[T1868] GetLastError(2845dc, 18f5ca4, 77c35292, 2803000e, ...) = 3
[T1868] TlsGetValue(0, 2845dc, 18f5ca4, 77c35292, ...) = 281ea0
[T1868] SetLastError(3, 2845dc, 18f5ca4, 77c35292, ...) = 7ffde000
...
[download]

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.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^3: Garbage collection problem?? (Win32 CRTL malloc) Download Code


good chemistry is complicated, and a little bit messy -LW
	PerlMonks