Having trouble getting the VS10 debugger to go to specific libraries?

I get debugger errors when using the serillazation boost library. To fix this, I am trying to get Visual Studio 10 to skip debugging the boost library, after I read it, I found out how this is achieved, but the solution somehow does not work. Here is a photo of redit.

http://i.stack.imgur.com/g24tO.png (dont have enough reputation to post it inside)

From what I read, this is the way to do it, but when debugging in VS10 it still gives me errors in force files. Can anyone see what I did wrong?

EDIT

The problem found with the solution was in the 32-bit part of regedit instead of 64, on which my system is turned on. However, changing this did not solve the problem. Here is a new picture.

+7
source share
1 answer

Here is a related post that will answer your question. How to skip common classes in VS 2008 at login?

You can do this by entering entries in the registry (I know this sucks). The key you are looking for ranges from 32 to 64 bits. For 32-bit systems, the key

HKEY_LOCAL_MACHINE \ Software \ Microsoft \ VisualStudio \ 9.0 \ NativeDE \ StepOver

If you are using 64-bit OS and 32-bit Visual Studio, the key

HKEY_LOCAL_MACHINE \ SOFTWARE \ Wow6432Node \ Microsoft \ VisualStudio \ 9.0 \ NativeDE \ StepOver

The Wow6432Node key is the key for 32-bit applications running on 64-bit systems. (Sidenote: a registry search for "_RTC_CheckEsp" will probably lead you to the right place, this is the default entry in Visual Studio 9)

The syntax should be familiar to you, but as an example, a simple entry might be the string value of boost ::. * = NoStepInto, which allows the debugger to switch to Boost. See http://www.cprogramming.com/debugging/visual-studio-msvc-debugging-NoStepInto.html for some other examples.

0
source

All Articles