[imp] Seg Faulting.. sigh

[Eli]

I had Horde/IMP segfault on me the very first time I set it up and tried
to use it.  I wasn't sure why it wasn't working, and then noticed apache
wasn't running and the error logs showed a segfault.  It hasn't
segfaulted since then yet though, but we will be testing it out with a
bunch of users...

As for the backtrace, I *think* that it looks like a memory allocation
error internally in PHP, but I'm not sure, it's been a real long time
since I looked at that stuff.

Eli.

-----Original Message-----
From: imp-bounces@lists.horde.org [mailto:imp-bounces@lists.horde.org]
On Behalf Of Rodolfo Segleau
Sent: Friday, August 16, 2002 1:18 PM
To: imp@lists.horde.org
Subject: Re: [imp] Seg Faulting.. sigh



> ----- Message from jfreeman@sporg.com ---------
>     Date: Fri, 16 Aug 2002 10:03:38 -0700
>     From: Jeremy Freeman <jfreeman@sporg.com>
> Reply-To: Jeremy Freeman <jfreeman@sporg.com>
>  Subject: [imp] Seg Faulting.. sigh
>       To: imp@lists.horde.org
> 
> 
> I posted earlier about my Apache randomly segfaulting for unknown
> reasons. I have finally managed to capture a backtrace of the event
and
> was _hoping_ someone out there could provide some insight into the
problem.
> 
> I am Running:
> 
> Apache/1.3.26 (Unix) with
> PHP/4.2.2
> mod_perl/1.27
> mod_ssl/2.8.10 OpenSSL/0.9.6e
> 
> PHP compiled with: './configure' '--with-mysql'
> '--with-apache=../apache_1.3.26/' '--enable-debug' '--with-gettext'
> '--with-imap=../imap-2002.RC2/' '--with-xml'
> 
> All compiled in static.
> 
> Kernel: Linux 2.2.19pre17
> 
> Here is the backtrace:
> 
> Starting program: /usr/local/src/apache_1.3.26/src/httpd -X -DSSL
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x2ad5f21c in malloc () from /lib/libc.so.6
> (gdb) bt
> #0  0x2ad5f21c in malloc () from /lib/libc.so.6
> #1  0x2ad5f074 in malloc () from /lib/libc.so.6
> #2  0x0818583b in zend_strndup (s=0x9184a38 "HORDE_ERROR", length=12)
at
> zend_alloc.c:356
> #3  0x0818c430 in zend_register_constant (c=0x7fffc270) at
> zend_constants.c:251
> #4  0x0819f399 in zif_define (ht=2, return_value=0x8f2737c,
> this_ptr=0x0, return_value_used=0)
>      at zend_builtin_functions.c:458
> #5  0x081bd19a in execute (op_array=0x8edae5c) at
./zend_execute.c:1598
> #6  0x081bf100 in execute (op_array=0x91841cc) at
./zend_execute.c:2141
> #7  0x081bf100 in execute (op_array=0x90cae4c) at
./zend_execute.c:2141
> #8  0x081bf100 in execute (op_array=0x8ea62c4) at
./zend_execute.c:2141
> #9  0x08196b79 in zend_execute_scripts (type=8, retval=0x0,
> file_count=3) at zend.c:810
> #10 0x080d1a91 in php_execute_script (primary_file=0x7ffff988) at
> main.c:1381
> #11 0x081a26dc in apache_php_module_main (r=0x8e68a74,
> display_source_mode=0) at sapi_apache.c:90
> #12 0x080cddc6 in send_php ()
> #13 0x080cde22 in send_parsed_php ()
> #14 0x081c77e9 in ap_invoke_handler ()
> #15 0x081dd54f in process_request_internal ()
> #16 0x081dd5b6 in ap_process_request ()
> #17 0x081d3f76 in child_main ()
> #18 0x081d4155 in make_child ()
> #19 0x081d42cc in startup_children ()
> #20 0x081d495d in standalone_main ()
> #21 0x081d51ec in main ()
> #22 0x2ad0a14f in __libc_start_main () from /lib/libc.so.6

Jeremy,

    I had a similar problem a while back. Now, I compiled PHP using
apxs, and 
tried to keep as dynamic as possible. Take a look at 
http://test.mechanus.org/info.php to see how i compiled it. I have not
really 
had problems with segfaults since then. I am running SuSE Linux on a 
AlphaServer with 2.4.4 kernel. 


Cheers, 

Rodolfo

-- 
IMP mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: imp-unsubscribe@lists.horde.org