Re: apc causing segmentation fault?

A backtrace from one of the core files would help. I did fix a segfault last week that I haven't committed yet which happens on a SIGTERM if APC is in the middle of executing a script when the signal hits. If your backtrace ends in a call to destroy_op_array() and somewhere further up the stack you see a call to just_die() then this is the segfault I fixed. -Rasmus On Mon, 2 Aug 2004, Shannon Werb wrote: > Hi All, > I have been on and off the list now for a while using APC asking lots of > questions. I am pleased with it but just started to notice a lot of seg > faults in my apache error log over the past few days, like the following: > [Mon Aug 2 17:32:58 2004] [notice] child pid 74907 exit signal Segmentation > fault (11) > [Mon Aug 2 17:33:00 2004] [notice] child pid 74935 exit signal Segmentation > fault (11) > [Mon Aug 2 17:33:00 2004] [notice] child pid 74338 exit signal Segmentation > fault (11) > [Mon Aug 2 17:33:02 2004] [notice] child pid 74339 exit signal Segmentation > fault (11) > > I did some digging on the internet and signal 11 usually indicates hardware > but when you read further lots talk about it being when apache references > memory it does not own? So I turned off APC to see what happened and it > went away immediately. > > My config is as follows: > extension="/usr/local/lib/php/extensions/no-debug-non-zts-20020429/apc.so" > > apc.shm_segments=5 > apc.shm_size=10 > apc.check_mtime=1 > apc.mmap_file_mask=/tmp/apc.XXXXXX > > Apache 1.3.27, php 4.3.8 (newly upgraded just last week, I did not notice > this under 4.3.7 but I didn't look closely either). > > Any thoughts on what I can do? > > Best Regards, > Shannon >