> No idea about the core dump -- it's not very usual > (for Python).
Definitely my experience. > However, you will have to do something about your > Python version. Either I checked, and as Jeremy said an update was just released recently; I've upgraded to 2.5.1. Thanks for the heads-up. > Is there sufficient debug information in the > coredump that can run "gdb > python core.dump" and see from the backtrace what is > actually causing > the problem? It certainly sounds like it would be In an unusually (for Ubuntu) boneheaded move, it looks like Ubuntu doesn't leave core files for packaged programs, even after a "ulimit -c unlimited". Any other way to pull this off? (The crash does seem to occur after Django authenticates with the database; I've turned sameuser authentication back on, and running the code as a different user generates a Python stack trace complaining of failed authentication.) Grant D. Watson, <[EMAIL PROTECTED]> ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
