1
Vote

Prevent breakpoint binding in stdlib when not enabled for debugging

description

I create a simple python project and as long as I am in that main program debugging works fine. However, if I put a breakpoint in a package that the main routine calls, the breakpoint is hit and execution stops. But at then step in/ step over do not work. Instead I have to put a breakpoint on every line that I want to look at.

I am using the VS2010 2.1 beta version, but this existed in 2.0 release (which is why I upgraded)

Thanks!

comments

Zooba wrote May 27 at 3:13 PM

You probably need to enable the "Enable debugging of the Python standard library" option under Tools\Options\Python Tools\Debugging (it's actually just a filename filter, so it will include any installed packages).

If this is enabled, or you're referring to a package that isn't installed into site-packages, let us know. Otherwise, we should look at renaming this option to make it clearer what it does.

ronnkling wrote May 27 at 3:18 PM

Yes! that was it. Thanks, I never would have found that on my own.

Zooba wrote May 27 at 5:02 PM

Actually, a better option would be for us to prevent breakpoints from binding when that option applies. Then you'll see a different icon and we can offer a tooltip.

Zooba wrote May 27 at 5:03 PM

(Updated title)

ronnkling wrote May 29 at 9:15 AM

I have now found a new way to get the same behavior. On Windows I have a C++ process that calls my python code that I was working with above. I attach to this process and the breakpoints in my Python code are hit, but again I can't step in/step out.