If a stack trace doesn't immediately make sense, you've got a corrupted stack. I got very mislead by corrupted stacks today-- boiled down to a buffer overflow -.-
On Wednesday, December 30, 2009, Skillet <[email protected]> wrote: > Ah thanks Jorge. That was confusing the hell out of me, good to know it's > something else. > > On Tue, Dec 29, 2009 at 5:55 PM, Jorge Rodriguez <[email protected]> wrote: > >> CBoundedCvar_Interp::GetFloat() in the stack trace is a red herring. The >> problem is never with that function but something else. I don't know why it >> always seems as if the stack trace passes through there, but it doesn't. >> It's recommended that you find a way to reproduce the problem on a local >> machine so that you can step through the code built in debug mode running >> in >> a debugger and figure out where it's going wrong. >> >> -- >> Jorge "Vino" Rodriguez >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlcoders >> >> > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > -- Thanks, - Saul. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
