On Tue, Dec 9, 2008 at 4:50 AM, Andrew Fong <[EMAIL PROTECTED]> wrote: > > When I'm poking around in my Django app, my development server > (manage.py runserver) will sometimes quit without raising an exception > or leaving any messages. I am not tinkering around with the code or > doing anything that would force a reload. It just decides to quit. > > I can check the last request I made before it crashed, but without any > exceptions or errors, it's very hard to debug. Does anyone have any > tips on getting some more useful output out of a crash?
I just ran into the same problem. In my case however, I happen to know exactly which requests causes the crash, it happened everytime I query a model (say Entry.objects.all()). So I ran: from myproj.myapp.models import Entry Entry.objects.all() from 'manage.py shell' and I immediately saw from the exceptions that there was an infinite recursion. It turned out that I defined a custom Manager's get_query_set() in a very wrong way causing an infinite loop (I stupidly returned self.filter(...) instead of calling super like the doc says). I don't know if this would help in your case, but I thought I share anyway, just in case. Ronny --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
