debugging vector exceptions

[Erarog]

Hello,

When I was trying to debug my project (with the standard debugger, on a windows pc), I stumbled upon a problem. When I tried to access an element out of range through the vector.at() function an exception was thrown and the program freezed. When I used the latest nightly build I noticed the debugger stopped in the header file, where the exception was thrown. Is there any way to find out which call to the vector.at() function caused the exception? Any help would be greatly appreciated.

[oBFusCATed]

You can use the callstack/backtrace window. It will show you all the list of function with has called the vector::at.
If you're using 10.05 or trunk nightly build I suggest to switch to debugger's branch nightly build,
because the switching to frame is know to be broken in these versions.

[Erarog]

Thank you, that worked.