> >Does anyone else experience segfaults?
>
> This is the first I've heard of segfaults in any component of Webware. I
> was just about to cut 0.5.1 this morning...
>
> I guess I'll hold off another day to see if anyone has comments on this.
>
> Could this be caused by a Python extension module such as postgres or
> something else?
>
> Also, can you provide more details about how you're running it?
> http://webware.sourceforge.net/More.shtml
I also thought it was weird that it would segfault.
My machine:
P3-600 running redhat 7.0 + updates.
The python setup:
python2.1 installed in /usr/local
psycopg 0.99.3 module (previous versions didn't work with DBPool)
mxDateTime (for psycopg)
mysql module (not being used in this application)
gtk and glade modules (not being used in this application)
ldap module (not being used in this application)
ogg module (not being used in this application)
A fairly minimal python setup.
Apache 1.3.20 using the mod_webkit adapter.
Running Webware using 'pythong Launch.py AsyncThreadedAppServer'.
Nothing has been modified except one config file were I changed to the
default context to my applications root directory. The PYTHONPATH i
start webware with only contains the path to my applicaitons root
directory.
The application is a simple website. There's a small database running
in postgresql, that I am accessing via DBPool. I have some classes to
represent the datastructures in python, and am doing relatively simple
queries.
Here's how I'm working:
Test pages.
Edit PSP and/or modules.
Restart webware.
Repeat.
I'm more than happy all source and data involved if you need that to
track it down. I was actually hoping to write this site up and have
everyone pick the design apart, and then write up the results as sort of
a Case Study.
jack.
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
