On Thu, Mar 18, 2010 at 10:29 PM, Kai Sterker <kai.ster...@gmail.com> wrote:
> Need to backtrack from there to find the issue. Could be caused by a > corrupt model, or a constellation we did not yet have in our previous > test worlds. Initial suspicion wasn't so bad at all. A classic case of stack corruption: (gdb) n Cannot access memory at address 0x0 Cannot access memory at address 0x0 270 return sqrt (squared_length ()); (gdb) bt #0 world::collision::update_movement (this=0xbfffdb84, positi...@0xbfffdb60, veloci...@0xbfffdb6c) at ../../../adonthell/src/world/vector3.h:270 #1 0x00000000 in ?? () (gdb) Problem is, issue could be anywhere before, so it won't be easy to track down. Need to find a tool to help with that. Hope valgrind will do ... Kai _______________________________________________ Adonthell-devel mailing list Adonthell-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/adonthell-devel
