http://code.google.com/p/modwsgi/wiki/InstallationIssues
http://code.google.com/p/modwsgi/wiki/ApplicationIssues
and have you also read properly:
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques
and taken note of how to run Apache in single process mode to allow it
to be debugged?
Graham
2008/8/8 gert <gert.c...@gmail.com>:
CFLAGS = -g
or possibly:
CFLAGS = -Wc,'-g'
if it doesn't like that.
Use 'where' command in gdb to get full traceback. With -g option will
hopefully then show line numbers for mod_wsgi at least.
State exactly which revision of mod_wsgi being used if using trunk, or
update to very latest revision, so I can know what code is at actual
line number in file quoted.
BTW, does the problem occur if you using mod_wsgi 2.1 tar ball rather
than anything from subversion.
Graham
2008/8/8 gert <gert.c...@gmail.com>:
Graham
2008/8/9 gert <gert.c...@gmail.com>:
if (wsgi_daemon_list) {
entries = (WSGIProcessGroup *)wsgi_daemon_list->elts;
for (i = 0; i < wsgi_daemon_list->nelts; ++i) {
entry = &entries[i];
close(entry->listener_fd);
entry->listener_fd = -1;
}
}
will crash embedded mode otherwise if no daemon processes defined.
Fixed in revision 981.
The code above was added when addressing leaking file descriptor issue.
Graham
2008/8/9 gert <gert.c...@gmail.com>: