[IronPython] How to do debugging for embedded usage

[Martin Maly]

Debugging in the first case style is something that's on our radar but we may not get to it for a while.
We don't have the in-process debugging interface or support for "pdb" yet. For now, we support Visual Studio or CLR debuggers (cordbg, DbgCLR.exe, ...)

Martin


________________________________

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Michael Latta
Sent: Wednesday, November 02, 2005 9:10 AM
To: 'Discussion of IronPython'
Subject: Re: [IronPython] How to do debugging for embedded usage


Is there any chance of supporting debugging for the first case?  I would rather persist the script sources with the document/repository rather than as files, though I could cache them on disk if needed.  Is there an in-process debugging interface I can use to support an embedded debugger rather than requiring VS be installed for the end-user scripting case?  For full fledge plug-ins VS would be good, but for true end-users something more targeted would be better.

Michael



________________________________

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Martin Maly
Sent: Wednesday, November 02, 2005 6:59 AM
To: Discussion of IronPython
Subject: Re: [IronPython] How to do debugging for embedded usage


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 helps
Martin


________________________________

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?

Michael

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20051104/8fe3c0c8/attachment.html>