You're not the first to experience segmentation faults with mod_python. :)
And, I'm not sure why it is occurring in your case. You seem to have
discovered a permission problem, and I can not explain why this should
propagate to a segmentation fault. I can tell you, though, that it likely
has absolutely nothing to do with Spyce. Rather, it's probably a certain
shared library that is linked in differently when running under an
Apache/mod_python process then when running standalone (i.e. FastCGI, CGI,
proxy, ...), or possibly a threading issue. It's difficult to know without
recompiling Apache/Python/mod_python with debug symbols and debugging the
problem, wherever it may lie. These things will get sorted out over time,
as mod_python continues to mature.
All the best,
On Thu, 16 Jan 2003, [ISO-8859-2] Przemys=B3aw Biel wrote:
>Hi, I had such problem:
>When I was trying to get some information form database (BerkeleyDB), I
>had such massege:
>...[notice] child pid 2590 exit signal Segmentation fault (11)
>in my error apache log and no response in my browser "the page does not
>have data" or sth. like this.
>But when I moved to Apache 1.2.27 and FastCGI I had this:
>DBAccessError: (13, 'Permission denied')
>Stack: ind.spy:4, in (main):
>pwinfo.py:21, in open:
>self.mydic =3D shelve.open(filename, mode)
>lib.linux-i686-2.2/bsddb3/dbshelve.py:69, in open:
>So, I understand my problem, because database had wrong permissions, but
>why spyce with mod_python caused segmentation fault ?
>I think it may be a bug in spyce code + mod_python.