Segmentation faults :(

[Michael Smith <mj...@iii.co.uk>]

Probably not a show-stopper but I'm seeing segmentation faults under
1.3.3 (also get them under 1.3.2); which look like this in the error
log:

[Wed Oct  7 16:20:52 1998] [notice] httpd: child pid 21631 exit signal
Segmentation Fault (11)
[Wed Oct  7 16:21:43 1998] [notice] httpd: child pid 21623 exit signal
Segmentation Fault (11)

We've not been able to get a core dump yet (we're trying to right now)
but did get a trace which went something like this:

write(8, " f u n d ' s   p r i c e".., 6896) (sleeping...)
write(8, " f u n d ' s   p r i c e".., 6896)    = 6896
read(9, " i t i e s < B R >  \n\n".., 8192)     = 4212
write(8, " i t i e s < B R >  \n\n".., 4212)    Err#32 EPIPE
    Incurred fault #6, FLTBOUNDS  %pc = 0x000613E8
      siginfo: SIGSEGV SEGV_MAPERR addr=0x00000030
    Received signal #11, SIGSEGV [caught]
      siginfo: SIGSEGV SEGV_MAPERR addr=0x00000030
chdir("/www/common")                            = 0
sigaction(SIGSEGV, 0xEFFFB0D8, 0xEFFFB158)      = 0
getpid()                                        = 12795 [9214]
kill(12795, SIGSEGV)                            = 0
setcontext(0xEFFFB2D8)
    Received signal #11, SIGSEGV [default]
      siginfo: SIGSEGV pid=12795 uid=60001
        *** process killed ***


We're running Apache/1.3.3 (Unix) mod_perl/1.16 with a couple of custom
mod_perl modules, which may confuse things a bit) on Solaris 2.5.1.
We've also seen a CPU increase since upgrading from 1.3b6/mod_perl 1.11,
but that may be due to other factors.

Anyone else seen something similar?

Cheers

Mike