On Sun, Nov 20, 2011 at 12:02 PM, Gunnlaugur Thor Briem <
[email protected]> wrote:
> I tried this in my setup, but the worker segfaults without informative
>> logging, when Django's WSGIHandler calls the uwsgi.start_response function.
>
>
>
I went and ran in gdb. The segfault is in this line:
wsgi_req->hvec[0].iov_base = (char *) http_protocol;
because wsgi_req->hvec is null.
So it seems like uwsgi indeed doesn't like start_response being called when
it doesn't agree that it has a current wsgi request.
- Gulli
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
