VB 2010 PRO Dbg doen't tell which line produces the error.

[eidge]

I've changed this week from C::B to VS2010 Pro.

When an exception that wasn't handled is thrown the debugger spitts out an error, like "Debug Assertion Failed, Abort, Retry or Continue".

I press retry and then a need window is openned "app.exe has triggered a break point"

This time I press continue a and similar window to the first one is openned explaining what happen. For instance "Standard C++ Libraries Out of range".

It also opens some source files that i didn't write like: stdthrow.cpp

Everything is fine till here, but shouldn't the debugger tell me which line of my code triggered the exception?

[andywestken]

The debugger should show you where the exception occured, wherever it is, along with the call stack. Back tracking up the call stack should show you what call in your code triggered off the events that led to the error.

Have you installed the Windows symbols on your machine yet?

[eidge]

I don't even know what those are, so I suppose I didn't.

http://msdn.microsoft.com/en-us/windows/hardware/gg463028

is this it?

[andywestken]

Well, ths page (linked from the one you posted) is the one I was thinking about.
http://support.microsoft.com/kb/311503/

You point your IDE at http://msdl.microsoft.com/download/symbols
Specify a local symbol cache directory
And go!

The first few times you use the debugger it can take a bit of time to drag down the symbols, but once the cache is up to date.

[eidge]

A new bar popped up with Process, Thread and Stack Frame.

Problem solved, thanks.