Re^2: No 'out of memory' message on Windows?

So LinkBlock didn't verify the pointer was valid before trying to link it into the list?

Comment on Re^2: No 'out of memory' message on Windows?

Replies are listed 'Best First'.
Re^3: No 'out of memory' message on Windows? by BrowserUk (Patriarch) on Feb 09, 2008 at 19:16 UTC
To be honest, I can't work out how it gets in there. The 100+ *alloc macros and functions in the Perl sources make it impossible to work out what is going on at the source level. And the use of C++ (style) classes for odd bits of the code, with runtime built dispatch tables throws my debugger's stack trace into loops. That means I can't follow it in that way. I can only tell you where it appears to be trapping. 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."	[reply]

Replies are listed 'Best First'.

Re^3: No 'out of memory' message on Windows?
by BrowserUk (Patriarch) on Feb 09, 2008 at 19:16 UTC

To be honest, I can't work out how it gets in there. The 100+ *alloc macros and functions in the Perl sources make it impossible to work out what is going on at the source level.

And the use of C++ (style) classes for odd bits of the code, with runtime built dispatch tables throws my debugger's stack trace into loops. That means I can't follow it in that way. I can only tell you where it appears to be trapping.

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."

[reply]