ok, this time i stepped into the first call and it turns out the return statement is throwing an exception inside it, and gdb's "step" and "nexti" commands do not step into the exception handler, instead continuing. the iterator theoretically steps to the next value and the breakpoint is hit again.
i'm guessing that i had let it run too many times last time, and some bug caused an overflow and memory corruption, maybe
