Re: [Ironpython-users] Enable Unmanaged Debugging IronPython

Hello, If I understand correctly, Zooba (on the Python Tools for Visual Studio team at Microsoft) suggested that IronPython isn't emitting proper debugging information so that the CLR debugger can find the correct lines of source code. Please see this thread: https://pytools.codeplex.com/workitem

Re: [Ironpython-users] Enable Unmanaged Debugging IronPython

Is there any debugger that allows stepping from IronPython to C# to C++? I tried just adding "import pdb; pdb.set_trace()" and running with "ipy64 -X:Tracing -X:FullFrames", but attempting to step into a C# function just stepped right over it. It seems that the PTVS debugger can't handle this eit

Re: [Ironpython-users] Enable Unmanaged Debugging IronPython

FYI, I posted this issue on https://pytools.codeplex.com/workitem/2538 . --- John's business hour MST availability (and John's availability in EST

Re: [Ironpython-users] Enable Unmanaged Debugging IronPython

Adding DinoV because this sounds more like a PTVS issue than an IronPython issue - from the IronPython side there's nothing that should prevent it from working AFAIK. IronPython in VS uses the normal managed debugger. - Jeff On Wed, Jul 9, 2014 at 12:04 AM, John DiMatteo wrote: > Hello, > > Wh

[Ironpython-users] Enable Unmanaged Debugging IronPython

Hello, While debugging, with an IronPython startup project, I'm trying to step from IronPython to C# code to unmanaged C/C++ code. Is this possible? I am currently able to step from IronPython to C# when the startup project is IronPython. I'm also currently able to step from C# to unmanaged C/C