Re: [Ironpython-users] WDB web debugger for IronPython

2015-05-06 Thread Jeff Hardy
Hi Kerray, Is there a GitHub issue for this open already? There probably is for missing co_lnotab, but about dis.findlinestarts failing strangely? Fixing co_lnotab shouldn't be difficult, but the compile error could be trickier. I'm assuming you haven't been able to reproduce it without wdb? You c

Re: [Ironpython-users] WDB web debugger for IronPython

2015-04-30 Thread Kerray
In other news, I've been trying to isolate the issue and finally found out that dis.py findlinestarts(code) is throwing a NotImplemented when trying to access code.co_lnotab, which is not implemented in IronPython - http://www.nudoq.org/#!/Packages/IronPython/IronPython/FunctionCode/P/co_lnotab So

Re: [Ironpython-users] WDB web debugger for IronPython

2015-04-29 Thread Kerray
Hi, it's been a while, but I've now again tried running the remote debugger https://github.com/Kozea/wdb client under IronPython. As J.Hardy wrote earlier, based on the stack trace I included: > Looks like one of the generator rewriters has a bug. I can't come up with a simple case to reproduce th

Re: [Ironpython-users] WDB web debugger for IronPython

2014-12-03 Thread Kerray
Hi Jeff, I've opened the issue with IPV6_V6ONLY - https://github.com/IronLanguages/main/issues/238 And I'll open one for the Tornado socket problem also. Other than that, I can successfuly run import wdb w = wdb.set_trace() in console and examine the contents of the resulting Wdb object (it seems

Re: [Ironpython-users] WDB web debugger for IronPython

2014-11-25 Thread Jeff Hardy
On Tue, Nov 25, 2014 at 12:32 PM, Kerray wrote: > Hi, > very good point, I've been on beta3. But the upgrade didn't help. I've > figured out how to debug the internals in VS, but there's nothing I could > be able to fix (or even understand) myself at this point. > > ad 1) after running wdb.server

Re: [Ironpython-users] WDB web debugger for IronPython

2014-11-25 Thread Kerray
Hi, very good point, I've been on beta3. But the upgrade didn't help. I've figured out how to debug the internals in VS, but there's nothing I could be able to fix (or even understand) myself at this point. ad 1) after running wdb.server, Tornado at first says \tornado\netutil.py", line 88, in bin

Re: [Ironpython-users] WDB web debugger for IronPython

2014-11-24 Thread Pawel Jasinski
hi, just to be sure,are you using 2.7.5RC1? If not, please try it. There were quite a few cpython compatibility improvements including socket module. On Mon, Nov 24, 2014 at 1:53 PM, Kerray wrote: > Hi everyone, > We're using IronPython to script the insides of SharePoint (ASP.NET on IIS). > For

[Ironpython-users] WDB web debugger for IronPython

2014-11-24 Thread Kerray
Hi everyone, We're using IronPython to script the insides of SharePoint (ASP.NET on IIS). For quite some time, I've been looking for a comfortable way to debug these scripts without having to install Visual Studio. I've considered using standard PDB, with console redirected over