Roberto De Ioris <roberto@...> writes: > Sorry i do know why i used uwsgi.start_response :) > > you can use a simple > > def fake_sr(status, hh, exc_info=None): > pass > > function instead of a real start_response, as you have no peer to send > data to
Oh, of course, I should have realized. But with the fake callback, it doesn't segfault, but it doesn't respond to requests either; it just doesn't respond to requests. The log output ends with: spawned uWSGI master process (pid: 50790) spawned uWSGI worker 1 (pid: 50793, cores: 1) adding 6 to signal poll and sending a request (via nginx) adds nothing. If I comment out my call to the application on init, I get this (in a debug build) after the "adding 6 to signal poll" line when I send a request: [uWSGI DEBUG] uwsgi payload size: 450 (0x1C2) modifier1: 0 modifier2: 0 [uWSGI DEBUG] PATH_INFO=/api/v1/info.json [uWSGI DEBUG] SERVER_NAME=localhost ... etc. and the request gets served just fine. (Didn't see your response before I sent the gdb followup --- that's what I get for only reading this list in digest mode. :) ) Regards, - Gulli _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
