On Dec 3, 2011, at 8:44 PM, Graham Dumpleton wrote:

> On 3 December 2011 05:50, Drew Yeaton <[email protected]> wrote:
>> Answers inline, though I'm not sure how helpful this will be—
>> 
>> On Dec 1, 2011, at 8:04 PM, Graham Dumpleton wrote:
>> 
>>> What Apache and Python versions?
>> 
>> Apache 2.2.8
>> Python 2.5.2
> 
> I haven't compiled with Python 2.5 for a very log time. It is possible
> that changes to threading to make it compliant with Python 3.2 could
> have broken things for 2.5.

What's the oldest Python you're planning to support?

> 
>>> Definitely not still loading mod_python into same Apache?
>> 
>> I don't believe so, but I don't know how to tell for sure.
>> 
>>> Is it the whole of Apache that is crashing, or just mod_wsgi daemon process?
>> 
>> Again, not sure how to tell.
> 
> Does the seg fault occur just once when Apache is started and Apache
> then doesn't seem to be running at all, or do you get a never ending
> loop of seg faults in log, or does seg fault only happen on first
> request made to a Python WSGI application?

Appears to happen just once. I attempted to start it multiple times, and got a 
single fault in the log for each attempt.

> 
> Graham
> 
>>> If need to get a stack trace, would need to follow steps in:
>>> 
>>>  
>>> http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Debugging_Crashes_With_GDB
>>> 
>>> and run httpd up under gdb with the -X option.
>>> 
>>> Graham
>>> 
>>> On 2 December 2011 12:58, Drew Yeaton <[email protected]> wrote:
>>>> I'm attempting to run mod_wsgi 4.0 (that I've compiled from the repo)
>>>> and it appears to be failing due to a segfault. The compile process
>>>> appeared to be fine, it's only when I start Apache do I have the
>>>> issue. I'm getting the following message in my logs:
>>>> 
>>>> apache2[1099]: segfault at 3 rip 3 rsp 4147d078 error 14
>>>> 
>>>> Thanks!
>>>> 
>>>> --
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "modwsgi" group.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to 
>>>> [email protected].
>>>> For more options, visit this group at 
>>>> http://groups.google.com/group/modwsgi?hl=en.
>>>> 
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "modwsgi" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to 
>>> [email protected].
>>> For more options, visit this group at 
>>> http://groups.google.com/group/modwsgi?hl=en.
>>> 
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "modwsgi" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to 
>> [email protected].
>> For more options, visit this group at 
>> http://groups.google.com/group/modwsgi?hl=en.
>> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "modwsgi" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/modwsgi?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to