[mod_python] Segmentation fault (11)

The document I referenced mentions a few of the main culprits.
http://code.google.com/p/modwsgi/wiki/ApplicationIssues

	Ok, Still have to get to that.


There are others besides subversion. What Python web application are
you trying to run which is causing it to crash? Does a simple hello
world example program work.

	I can't even load a generic non-python page when that module is
	loaded. When I try and access any webpage I get the seg fault.
	If the module is loaded I cannot access the default apache web
	page. If the module is not loaded, then I can access the default
	apache web page.

If nothing shows up as being obvious, you will need to determine where
the crash is occurring. For details on debugging crashes in Apache
using gdb see:

  http://code.google.com/p/modwsgi/wiki/DebuggingTechniques

	Thanks, I may need to do that. I've never done it before but I 
guess there is always a first time. Also its something good to know.

BTW, please use reply-all and keep follow ups on mailing list.

Sorry, I will try and remember that.


--Mike
 

-----Original Message-----
From: Graham Dumpleton [mailto:graham.dumpleton at gmail.com] 
Sent: Thursday, October 04, 2007 7:05 AM
To: Michael Robokoff
Cc: mod_python
Subject: Re: [mod_python] Segmentation fault (11)

On 04/10/2007, Michael Robokoff <mike.robokoff at apioutsourcing.com> wrote:
> Thank you for the response, I appreciate your help.
>
>
> Segmentation faults like this can be caused by a number of issues.
>
> 1. Linking in of multiple versions of the same shared library which
> are incompatible.
>
>         How do I find out about this?

The document I referenced mentions a few of the main culprits.

> 2. Linking in of a shared library that conflicts with embedded expat
> or SSL support code in Apache.
>
>         I did verify the expat libraries are the same. I don't have any
>         problems with ssl. It is only when mod_python is loaded that the
>         problem occurs.
>
> 3. Third party Python extension modules that aren't designed to work
> in sub interpreters, for example, subversion bindings.
>
>         I didn't install any of these.

There are others besides subversion. What Python web application are
you trying to run which is causing it to crash? Does a simple hello
world example program work.

> 4. Broken Python installations on Debian systems whereby they screwed
> up md5 module causing conflicts with md5 code in PHP.
>
>         I am running on Solaris 10, and built Python my self with out
>         any issues.
>
> You might have a look through:
>
>   http://code.google.com/p/modwsgi/wiki/ApplicationIssues
>
> Although this is for mod_wsgi, a lot of those issues apply to mod_wsgi as
> well.
>
>         Thanks again, I will check it out.

If nothing shows up as being obvious, you will need to determine where
the crash is occurring. For details on debugging crashes in Apache
using gdb see:

  http://code.google.com/p/modwsgi/wiki/DebuggingTechniques

BTW, please use reply-all and keep follow ups on mailing list.

Graham

> --Mike
>
> Graham
>
> On 04/10/2007, Michael Robokoff <mike.robokoff at apioutsourcing.com> wrote:
> >
> >
> >
> >
> > I was having trouble integrating mod_python-3.3.1 with apache 2.2.6 Both
> > were compiled from source.
> >
> > I would get the following anytime I tried to access any web page.
> >
> >
> >
> > [notice] child pid 8625 exit signal Segmentation fault (11), possible
> > coredump in /usr/local/apache2
> >
> >
> >
> > I wound up going back to mod_python-3.2.10 and all seems to work now.
> >
> >
> >
> > Anyone else seeing this kind of problem?
> >
> >
> >
> >
> >
> >
> >
> > Michael Robokoff
> >
> > Senior Systems Administrator
> >
> > API Outsourcing
> >
> >
> >
> >
> > _______________________________________________
> > Mod_python mailing list
> > Mod_python at modpython.org
> > http://mailman.modpython.org/mailman/listinfo/mod_python
> >
> >
>
>
>