|
Graham Dumpleton
grahamd at dscpl.com.au
Mon May 23 16:59:06 EDT 2005
Known problem.
As a start, read:
http://www.modpython.org/FAQ/faqw.py?
query=mod_php&querytype=simple&casefold=yes&req=search
In summary it is generally because parts of mod_php have been compiled
against different versions of shared libraries than mod_python.
Search through the mailing list archives for previous posts about this
from the mod_python web site home page.
Graham
On 24/05/2005, at 2:27 AM, Martin Lesser wrote:
> This may be OT on this list so please take my apologies for this
> posting.
>
> I need a pointer which is the right address to report an IMO serious
> bug which is _not_ caused by mod_python but occurs when using it.
>
> We use mod_python since several months with success, yesterday we
> extended some modules to use cdb-files with python-cdb
> (http://pilcrow.madison.wi.us/)
>
> The apache 2.0.54 (gentoo-linux) running mod_python also loads mod_php
> (4.3.11) and simple code like
>
> | from mod_python import apache, util
> | import cdb
> | def index(req):
> | _c = cdb.init('any_cdb_file.cdb')
> | _x = _c.get('any_key') # This line caused the segfault, not the
> init
> | return '<html>%s</html>' % _x
>
> caused a segmentation fault.
>
> After recompiling mod_php several times with reduced options
> (--disable-dba, --disable-dbx, --without-cdb etc.) the code above
> worked
> as expected.
>
> How is it possible that one modul (mod_php) causes a segfault in the
> main program (apache) when this program executes code from another
> modul
> (mod_python)? Is this an apache-bug?
>
> What's the right place to report this bug?
>
> TIA, Martin
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://mailman.modpython.org/mailman/listinfo/mod_python
|