Just a hunch, but you might want to try passing "-X:MaxRecursion 1000" to ipy.exe. By default, IronPython has a very high recursion limit compared to CPython. On occasion this can cause the entire interactive session/process to die with a StackOverflowException rather than emit a catchable Python RuntimeError.
The other thing is if you're running under an x64 OS, try ipy.exe instead of ipy64.exe. ipy.exe is purely a 32-bit CLR process and hence needs less memory. Hope that helps, Dave -----Original Message----- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jeff Hardy Sent: Wednesday, October 28, 2009 7:30 AM To: Discussion of IronPython Subject: Re: [IronPython] Django 1.1 on IronPython 2.6rc2 findings 2009/10/28 Markus Törnqvist <m...@nysv.org>: > At this point I run into my skill deficiency; as I'm presented with the > options to Debug or Close and Debug doesn't tell me anything, I dunno > how to debug this. > > Any hints? If you run ipy with the -D flag (or set system.compilation/debug=true for NWSGI) then IronPython will emit debug symbols; otherwise you won't be able to actually debug the Python code. You can then attach Visual Studio to the process (which clicking "Debug" should do) and step through the Python code. Note that debugging isn't always perfect, but it at least gives you an idea where to look. - Jeff _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
