RE: [hlcoders] memoverride.cpp voodoo!

2005-10-02 Thread Alfred Reynolds
@list.valvesoftware.com Subject: Re: [hlcoders] memoverride.cpp voodoo! Alfred Reynolds wrote: You need to link to the static C libraries and not the dynamic ones. Memoverride.cpp causes the link to use our version of malloc(), free(), etc when using the static library (and these calls all get directed

[hlcoders] memoverride.cpp voodoo!

2005-10-01 Thread Jorge Rodriguez
It's been a while since I've been on this list... since November I think. I have a real stumper for my first question. This is not for the faint of heart, but it is a challenging problem that needs to be solved in the long run (and I hope has already been solved by someone that I haven't found

RE: [hlcoders] memoverride.cpp voodoo!

2005-10-01 Thread Alfred Reynolds
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jorge Rodriguez Sent: Saturday, October 01, 2005 2:57 PM To: hlcoders@list.valvesoftware.com Subject: [hlcoders] memoverride.cpp voodoo! It's been a while since I've been on this list... since November I think. I have a real stumper for my first

Re: [hlcoders] memoverride.cpp voodoo!

2005-10-01 Thread Jorge Rodriguez
Alfred Reynolds wrote: You need to link to the static C libraries and not the dynamic ones. Memoverride.cpp causes the link to use our version of malloc(), free(), etc when using the static library (and these calls all get directed into the tier0 memory management code). - Alfred Total utter