I can't say I know very much about the particular module you're using. However, it seems to me that you should use strategically placed print statements (or some other output) to determine where the program dies so that you can single out the exact statement or statements where the program dies and whatever parameters are being used at that point. (Pretty much standard debugging procedure.) This way you don't have to rely on a debugger and OS error messages.
Once you do so (or if you've already done so), by providing the problem code and input, fellow monks may be more able to help you.
Zenon Zabinski | zdog | firstname.lastname@example.org