Re: Django crashes Python without traceback on Mac OS X (Release 1.0)
On Oct 20, 11:34 am, "jd.strickler" <[EMAIL PROTECTED]> wrote: > Just as a heads up: if you have a 64-bit Intel chip running OS X > > The cross-compiling/Universal Binary issue may come up to bite you (it > did me). Apache runs in 64-bit mode while most of the system runs in > 32-bit mode, meaning that every part of your Django stack has to be > compiled for both into a UB. > > Specifically, I had to hack around with mod_python, Postgresql, > psycopg2, and python-ldap (for an LDAPBackend I wrote; not needed for > a vanilla Django setup). Ccompiling this stuff correctly usually > means adding a few tags in the right file. > > (Because I'm an idiot) this took me ~2 months to get right. So, if > you solve your stack overflow issue and run into any of these, email > me and I'll send over the documentation I have. Or you force Apache to run in 32 bit more. For details see: http://code.google.com/p/modwsgi/wiki/InstallationOnMacOSX#Thinning_The_Apache_Executable Plus comment to same document which explains easier way by changing plist file. Graham --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Django crashes Python without traceback on Mac OS X (Release 1.0)
Just as a heads up: if you have a 64-bit Intel chip running OS X The cross-compiling/Universal Binary issue may come up to bite you (it did me). Apache runs in 64-bit mode while most of the system runs in 32-bit mode, meaning that every part of your Django stack has to be compiled for both into a UB. Specifically, I had to hack around with mod_python, Postgresql, psycopg2, and python-ldap (for an LDAPBackend I wrote; not needed for a vanilla Django setup). Ccompiling this stuff correctly usually means adding a few tags in the right file. (Because I'm an idiot) this took me ~2 months to get right. So, if you solve your stack overflow issue and run into any of these, email me and I'll send over the documentation I have. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Django crashes Python without traceback on Mac OS X (Release 1.0)
alternatively you can also try to reduce recursion limit by using sys.setrecursionlimit() to lower setting which might help you to debug the offending secton of code. vp --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Django crashes Python without traceback on Mac OS X (Release 1.0)
On Sat, Oct 18, 2008 at 4:16 PM, Brian <[EMAIL PROTECTED]> wrote: > > Hi there, > > Django is crashing Python on my machine for one particular application > of my Django project (the other applications are unaffected). It's on > the Django 1.0 development server, Mac OS X 10.5.5, stock Python > 2.5.1. > > There is no trace-back. Removing cookies and .pyc files does not > resolve the problem. I'm not sure how to go about debugging it. > Thought I'd share. :) > It looks like you're overflowing the stack. I recall one bug a couple of months ago that caused infinite recursion generated error reports like this on some machines (where elsewhere it was reported as maximum recursion depth exceeded). So one way to debug might be to try it on a different machine - different architecture, different OS, different versions of things just to see if you can get better diagnostics as to what is going on. If that's not feasible I'd add logging/print statements to try to isolate where you are in your code before things go south. Karen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
