Cortex wrote: > A good tool to use in this case could be "Call stack". Sometimes I had > similar problems and thanks to the Call Stack, I've found what pointer > pointed to null :)
That works when you pass a null pointer as an argument to the code that crashes. In my case, no code of mine, (or address code outside the engine for that matter) was on the stack at all. I found the problem, but it was very painfull. That's one reason I don't like to work on anything where I don't have ALL the source. Ralph Hartley _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
