I inadvertantly saw one crash when doing something else, but can't otherwise duplicate it. Let me know if you ever work out a narrow use case or example which reliably shows it.
I'm going to go back to more important things for the time being. Graham 2009/2/17 Graham Dumpleton <[email protected]>: > 2009/2/17 gert <[email protected]>: >> Here is the deal, first you let the a interpreter crash (500) syntax >> error or something, then when you want to clean up that specific >> crashed interpreter, boom segfault :) >> >> [Tue Feb 17 00:49:22 2009] [info] mod_wsgi (pid=7085): Destroy >> interpreter '127.0.0.1|/appwsgi/www/invoice/invoice.wsgi'. >> [Tue Feb 17 00:49:22 2009] [info] mod_wsgi (pid=7085): Cleanup >> interpreter ''. >> [Tue Feb 17 00:49:22 2009] [info] mod_wsgi (pid=7085): Terminating >> Python. >> [Tue Feb 17 00:49:23 2009] [notice] child pid 7085 exit signal >> Segmentation fault (11) > > Thanks for trying to narrow it down. I'll try with exceptions at > global scope on first import and within request handler itself. Likely > I am not clearing some exception state properly, or leaving a > reference to object which has since been destroyed. On shutdown > probably checking the value and so crashing. > > Graham > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
