Re: [SM-USERS] SM Causing Apache to Segfault

2006-02-14 Thread Josh Baird
Ok, I have fixed the problem by rebuilding all of my PHP extensions once again. Chris Hilts wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Baird wrote: I am having problems with 1.4.6rc1 which is causing Apache to segfault everytime I try to access the login page of SM. Here

Re: [SM-USERS] SM Causing Apache to Segfault

2006-02-14 Thread Josh Baird
It is at 32MB. Frank Bonnet wrote: Josh Baird wrote: I am having problems with 1.4.6rc1 which is causing Apache to segfault everytime I try to access the login page of SM. Here is some information about my system and installation.. FreeBSD 5.3-rel-p20 SquirrelMail 1.4.6rc1 Apache 1.3.27

[SM-USERS] SM Causing Apache to Segfault

2006-02-13 Thread Josh Baird
Segmentation fault (11) [Tue Feb 14 00:35:42 2006] [notice] child pid 89904 exit signal Segmentation fault (11) --- Can someone please give me a hand with this issue? Thanks, Josh Baird --- This SF.net email is sponsored by: Splunk Inc. Do you grep

Re: [SM-USERS] Problems with v1.4.4

2005-02-04 Thread Josh Baird
Ok, checked a few more logs. My /var/log/httpd-error.log has: [Fri Feb 4 11:05:04 2005] [notice] child pid 79956 exit signal Segmentation fault (11) [Fri Feb 4 11:05:04 2005] [notice] child pid 79955 exit signal Segmentation fault (11) It look's like it segfaults everytime someone tries to ac

Re: [SM-USERS] Problems with v1.4.4

2005-02-03 Thread Josh Baird
Actually, now it's just a blank page. The connection does not drop. Josh Baird wrote: I am using Apache 1.3.27, SQ 1.4.4, and PHP 4.3.10, Fbsd 5.2.1. After upgrading PHP via ports, I had to recompile and get rid of the configure option '--disable-all' which disabled se

[SM-USERS] Problems with v1.4.4

2005-02-03 Thread Josh Baird
I am using Apache 1.3.27, SQ 1.4.4, and PHP 4.3.10, Fbsd 5.2.1. After upgrading PHP via ports, I had to recompile and get rid of the configure option '--disable-all' which disabled sessions. Sq was complaining about not being able to use sessions. This fixed that problem, but created another o