Hey all,
On Tue, Nov 11, 2008 at 8:18 PM, dan90 <[EMAIL PROTECTED]> wrote:
>
> I've been fighting a nearly identical bug to Robert for a while now
> too, in fact, but his greater gdb-fu has got him further. my problem
> description of the problem is nearly identical:
w00t! well. not for you, But i'm glad to know i'm not the only one.
> My production server, which doesn't have the problem, is Ubuntu Hardy,
> 64 bit throughout. python 2.5. (Rob, I'm assuming that you have built
> a custom mod_wsgi for Feisty, since my modwsgi version for Hardy shows
> as 1.3)
> my dev server, which crashes reproducably on accessing URLs which load
> the GEOS library, is Ubuntu Intrepid, 64 bit throughout also.
Yes, our mod-wsgi 2.0 was custom compiled for feisty.
Latest updates: A really simple wsgi app that does the following for a
request explodes nicely in the same way.
from myproject.myapp.models import MyModel
def application(environ, start_response):
status = '200 OK'
output = 'boo!\n'
o = MyModel.objects.get(pk=1)
g = o.some_geomtry // boom!
output += str(g)
response_headers = [('Content-type', 'text/plain'),
('Content-Length', str(len(output)))]
start_response(status, response_headers)
return [output]
I wondered if it was something to do with psycopg2 but I just ran the
django-gis db & model tests on intrepid and it didn't segfault. The
django-gis geos unit tests pass too. Maybe i should run the geos tests
inside a wsgi request...
back to my digging...
Rob :)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
