[federico2929]

Hi,

Since the last two python versions I have been having python die with the following exceptions

Application closed:
Py_1489399231 KERN-EXEC 3

I don't know exactly whats killing it, since it dies in a very large application that I have been developing for the last year and a half.

Does anybody know how to find out what is killing it?

Can I catch this sort of exceptions?

I am running the latest python, signed, and a N95

[jplauril]

Originally Posted by federico2929

Hi,

Since the last two python versions I have been having python die with the following exceptions

Application closed:
Py_1489399231 KERN-EXEC 3

I don't know exactly whats killing it, since it dies in a very large application that I have been developing for the last year and a half.

Does anybody know how to find out what is killing it?

Can I catch this sort of exceptions?

I am running the latest python, signed, and a N95

This error means that a background thread started by your application crashed. KERN-EXEC 3 is a generic error, essentially the equivalent of "Segmentation fault" in Unix.

[jplauril]

One the most common things that causes this is trying to use native resources from a different thread than where they were created in.

[federico2929]

Is there anyway to catch that exception? or to see where in the code its happening?

Thanks

[miohtama]

Originally Posted by federico2929

Is there anyway to catch that exception? or to see where in the code its happening?

Thanks

You need have try...except block in the starter function of your thread. Then pass this exception to the main thread and print it there.

More robust solution is multithread aware logger. I have created one, but it is not yet publicly available.