2005/11/2, Martin Maly <[EMAIL PROTECTED]>:
It largely depends on how your Python scripts are written. If you use following format:engine.Execute("print "Hello")debugging is hard because IronPython has no source code to map debugging info to.On the other hand, if you have your scripts stored in the files and execute them via:engine.RunFile(fileName);then IronPython generates debug info and debugging is straightforward - attach debugger to your app and place breakpoint into the Python source file and things mostly work as you'd expect. There are some rough edges to be polished, but debugging this way is quite good already.Hope this helpsMartin
From: [EMAIL PROTECTED] ironpython.com [mailto:[EMAIL PROTECTED]ironpython.com] On Behalf Of Michael Latta
Sent: Tuesday, November 01, 2005 8:59 PM
To: 'Discussion of IronPython'
Subject: [IronPython] How to do debugging for embedded usageWhen I am using IronPython within my application (for scripting/extension) how do I support debugging? Is there an event in the engine when a break point is hit? How do I specify to the engine that there is a break point? I presume I need to provide an editor and such myself, as well as a UI for examining the run-time state? I presume I can use the stack walker for examining the stack?Michael
_______________________________________________
users mailing list
[EMAIL PROTECTED] ironpython.com
http://lists. ironpython.com/listinfo.cgi/users-ironpython.com
--
The shift of focus (to patterns) will
have a profound and enduring effect
on the way we write programs.
--Ward Cunningham and Ralph Johnson
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
