[IronPython] How to do debugging for embedded usage
Martin.Maly at microsoft.com
Fri Nov 4 16:08:53 CET 2005
Because it it generated as a code snippet into the snippet assembly which doesn't have association with the source file and therefore the debugger cannot make the connection between the code and the source file.
I'm going to look into whether this could get changed/fixed.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Angelo Xu
Sent: Friday, November 04, 2005 3:18 AM
To: Discussion of IronPython
Subject: Re: [IronPython] How to do debugging for embedded usage
why engine.ExecuteFile(fileName) can't be debuged
2005/11/2, Martin Maly <Martin.Maly at microsoft.com>:
It largely depends on how your Python scripts are written. If you use following format:
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:
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 helps
From: users-bounces at lists. ironpython.com [mailto:users-bounces at lists.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 usage
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?
users mailing list
users at lists. 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users