dinov at exchange.microsoft.com
Fri Mar 7 20:13:39 CET 2008
One thing that might help is running w/ -X:ExceptionDetail to get the full .NET stack trace.
I also suspect this exception must be coming from the finalizer thread or from a newly created thread. Is your app multi-threaded? If you create threads w/ Python's thread module then your threads won't rip the process. In .NET 2.0 the CLR started ripping the process whenever there's an unhandled exception but we wrap new threads w/ an exception handler when starting from thread.
Other than the fact that it looks like it's on a new thread though it looks like you're calling a method with null as the value and it's expecting an int32. Unfortunately we're not giving you a very useful stack trace. Seeing the full .NET stack trace would be interesting because there's probably something we can do to make this better.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Harri Vartiainen
Sent: Friday, March 07, 2008 10:24 AM
To: Discussion of IronPython
Subject: [IronPython] Crash
I got my callback eventually working and found one bug/problem:
If the callback function returns invalid type (eg. None), the
Traceback (most recent call last):
File , line 0, in System.Int32(Int32, Double, IntPtr, Int32)##154
TypeError: Cannot convert NoneType() to Int32
And then Windows displays the "program crashed - report to Microsoft" -dialog.
Users mailing list
Users at lists.ironpython.com
More information about the Ironpython-users