<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.3790.2541" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2>It largely depends on how your Python scripts are written.
If you use following format:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2>engine.Execute("print "Hello")</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2>debugging is hard because IronPython has no source code to
map debugging info to.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2>On the other hand, if you have your scripts stored in the
files and execute them via:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2>engine.RunFile(fileName);</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2>Hope this helps</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=131465314-02112005><FONT face=Verdana
color=#800000 size=2>Martin</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> users-bounces@lists.ironpython.com
[mailto:users-bounces@lists.ironpython.com] <B>On Behalf Of </B>Michael
Latta<BR><B>Sent:</B> Tuesday, November 01, 2005 8:59 PM<BR><B>To:</B>
'Discussion of IronPython'<BR><B>Subject:</B> [IronPython] How to do debugging
for embedded usage<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=968584604-02112005>When 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?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=968584604-02112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=968584604-02112005>Michael</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=968584604-02112005></SPAN></FONT> </DIV></BODY></HTML>