This is driving me crazy. I'm finding it hard to make a simple testcase.
I use a custom handler and somewhere in the code I do this:
-- [snip] -------------------------------------------------------------
from mypackage.mysubpackage.mysubsubpackage import db
def run(req):
req.sess['foo'] = object
# req.sess['foo'] = db
req.sess.save()
return
# I redirect the user another path with util.redirect and then the segfault
# happens
----------------------------------------------------------------------
The moment I try to assign my own classes (ie: assigning db instead of object I
must manually delete the pysid cookie to stop the segfaults.
It seems as if mp corrupts or somehow leaves in an usable state the session
after trying to save my objects. I tried with different objects and it happens
with all of them. Does anyone knows how I can retrieve more info from the
segfault? I don't like segfaults :( they don't tell why they don't like you.
dharana wrote:
More information about the segfault. It always happens after a certain
ammount of time. I believe it maybe this:
- session starts correctly
- I navigate throught many pages
- session timeouts
- segfault
It's just a supposition, I will try to confirm it.
I couldn't reproduce it with MemorySession because I use apache
multithreaded and when I tried to use DbmSession it throws an Exception
in the do_save() function. I'm using mod_python_20050518163650.tar.gz
with the typo bug I reported (
http://issues.apache.org/jira/browse/MODPYTHON-45 ) fixed.
I will report if I find out more info or I find an easy to reproduce
testcase.
--
dharana
