|
It’s good to hear that it’s
fixable. But, off course, here’s the next one J. With the same little script: x = 1 y = 2 def Add(a, b): x = a + b return x z = Add(x, y) print z And the following C# code: EngineOptions options = new
EngineOptions(); options.ClrDebuggingEnabled = true; PythonEngine _pe = new
PythonEngine(options); delegate int Add(int a, int b); _pe.ExecuteFile(@" script
path "); Add add = _pe.EvaluateAs<Add>("Add"); int var1 = add(2, 3); int var2 = add(3, 4); The following happens: (I use a release version of Ironpython
(RC2). There are no debug symbols present, so that I don’t step into the
engine code.) I step into ExecuteFile (F11) and get into
native code. After a few lines of native code, I can go back to the source code
view and I’m in the Python script file. Maybe this is a similar issue as
with stepping into a function? Next, I get a delegate to the Python Add
function. The first time I step into the add delegate I get the stepping into a
function problem and then I’m inside the function. But, when I try to
step into the next add delegate this doesn’t work anymore: the line is
marked in green in Visual Studio and I remain in the C# code. The next step
into command resumes on the next line in the C# code. I can’t see a
reason why it would fail with the next add. Setting a breakpoint in the Python
function stops the execution at that point in both cases. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shri Borde I have opened this
bug - http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=2248
- to track the issue with stepping in. We are not emitting any line number
information for IL offset 0. |
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
