New submission from Dmitry Groshev lambdadmi...@gmail.com:
Here is a console output:
si14@si14-work:~/repos/monitoring/root$ python2.7 server.py
127.0.0.1 - - [2011-01-28 12:29:30] GET /update HTTP/1.1 200 320 -
Python-urllib/2.7
Dmitry Groshev lambdadmi...@gmail.com added the comment:
I should also say that this bug appears at first time, but it doesn't make it
less scary. The packet that crashed python was the same as the one shown and
I've already used this tiny server for a day or two without modifications, so
it
Dmitry Groshev lambdadmi...@gmail.com added the comment:
Ok, I've played with this some more and got some more segmenation faults. It
looks like a gevent problem, but I think that python shouldn't completely fall
so easy. Here is more traces:
si14@si14-work:~/repos/monitoring/root$ python2.7
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
I don't reproduce the issue. Could you run python under gdb and give us the C
backtrace?
--
nosy: +amaury.forgeotdarc
___
Python tracker rep...@bugs.python.org
Dmitry Groshev lambdadmi...@gmail.com added the comment:
I've changed gevent.wsgi server to gevent.pywsgi and it works as expected. Now
I switched it back to gevent.wsgi and it doesn't crash too! That's strange, but
I understand that you can't fix it without normal backtrace. I'm sorry for the
Brett Cannon br...@python.org added the comment:
Closing as invalid since gevent seems to be the culprit of the segfault.
--
nosy: +brett.cannon
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
