Running an old IronPython on newer mono #1473
Comments
I don't even know what version of IPy that is...it seems like something built locally? |
The problem occurs with later IronPython versions too, it seems. In any event, we found a workaround of supplying -X:ExceptionDetail (or setting that property in code). |
Actually, we aren't crashing anymore, but aren't getting Python stack traces either. |
What later versions of IronPython have you tried? |
I haven't... working with another developer. He said that he is getting the same problem with NET35 with newer IronPython. |
here is a full crash report: https://bitbucket.org/ipre/calico/issues/222/large-number-crash |
I updated our Python & Microsoft.Scripting DLL's and still have the same crash as Doug mentions. It appears to stem from
|
Did you also update the standard library files? There were some updates to that as well in 2.7.6.3. Also, can you tell me what versions of mono and ironpython were previously working? |
I'll update the standard libraries as well, I didn't do that. Currently using:
I'm not sure what I was using previously, but it was the Ubuntu 14.04 apt-get. (Maybe 3.2.8?) And as Doug mentioned, we are using an older (non-standard?) version of IronPython:
|
@slide 2.9.9 is probably a build of the master branch. |
@slozier Makes it pretty difficult to determine what code base was being used... |
OK, I've tried to recreate our issue with a simple embedding of IronPython:
which results in:
Ubuntu 14.04 |
Does this same code work on Windows? Just trying to narrow down if it is something mono specific. |
I just tested on Windows and it works (gets a correct stack trace). So, there is something specific to mono. |
The issue seems to be that StackFrame.GetMethod() is returning null on Mono, but not on Windows (MS.NET). So, this could be an issue with Mono itself. We'll have to look into it further. |
Thanks for verifying it works on windows, I should have mentioned earlier we noticed the trouble on Mac OS X. |
Just as an FYI, we're really just recently trying to get things work on Mono. We have a large portion of tests now running and passing on Mono, but there are sure to be issues like this one until we get a full support story going for Mono. |
Great to hear development is going strong! We've been using IronPython on Mono from the start of our Calico project (2008 or so) and have had little headaches with that part of the Mono experience (Gtk on the other hand ...). |
I posted an issue on the Mono bug tracker: |
Thanks for all the work on this! |
This issue was moved to IronLanguages/ironpython2#27 |
Running into a case with an old ironpython (2.9.9a0) on new mono (such as 4.2.1):
Above the exception is handled somewhat, but with a weird error message. Any quick fix other than upgrading ironpython?
The text was updated successfully, but these errors were encountered: