1

Closed

import scipy on IronPython causes us to stop hitting breakpoints

description

Install IronPython 2.7, and scipy.net
Open attached project.
F5 -- the breakpoint on line 3 is hit.
Change line 1 to: import scipy
F5 -- the breakpoint on line 3 is not hit
Change Project->Properties->Launch mode to IronPython (.NET) Launcher
F5 -- the breakpoint on line 3 is hit

Expected: we should always hit the breakpoint on line 3.

file attachments

Closed Sep 13, 2011 at 9:10 PM by joxn

comments

dinov wrote Sep 9, 2011 at 11:57 PM

Workaround added in 1.1 - http://pytools.codeplex.com/SourceControl/changeset/changes/fa51a2f43484

This is an IronPython bug: http://ironpython.codeplex.com/workitem/31437

I've implemented a workaround where we manually track the frames list on IronPython instead of relying upon the linked list of frames to be valid. If you want to get this working immediately in your own copy of PTVS you could look at the diff and apply it to visualstudio_py_debugger.py. That file lives in either VisualStudioInstallDir\Common7\IDE\Extensions\Microsoft\Python Tools for Visual Studio\1.0 or %LOCALAPPDATA%\Microsoft\VisualStudio\10.0\Extensions\Microsoft\Python Tools for Visual Studio\1.0 depending on if you did a per-machine (the default) or per-user install.