[solved] Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Hello and thanks for your feedback! On Tue, 2010-11-16 at 13:03 +0100, end...@gmail.com wrote: [...@pandora ~]$ php -v -c /usr/local/etc/php.ini-production PHP 5.3.2 with Suhosin-Patch (cli) (built: Jun 14 2010 18:11:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) Here's what did it for me : remove the following lines from /usr/ports/textproc/libxml2/files/patch-configure and rebuild+reinstall libxml2 @@ -20678,6 +20679,8 @@ fi fi fi ;; + *freebsd*) THREAD_LIBS= + ;; esac if test $WITH_THREADS = 1 ; then THREAD_CFLAGS=$THREAD_CFLAGS -D_REENTRANT I found this somewhere but cannot remember the thread url unfortunately... Brillant! It fixed the issue, many thanks. CC'ing both ports manager (pecl-imagick and libxml2). It would be nice if this could be fixed in the ports tree directly: are these patch lines still required by other packages? Regards, Olivier PS: something probably related is visable under http://forums.freebsd.org/archive/index.php/t-8965.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [solved] Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Hi Alex, thanks for this even better feedback. On Tue, 2010-11-16 at 15:22 +0100, Alex Dupre wrote: This is not the correct fix, the correct fix is to enable threads in php, using the appropriate OPTION. Ok, so probably this one: LINKTHR=off (default) Link thread lib (for threaded extensions) - on Is there any chance this will have other consequences (problems, incompatibilities with other php/pecl extensions) ? Or why is this off by default ? This should at least be checked when installing pecl-imagick, and I presume it will happen sometime as there is already PR about this case: http://www.freebsd.org/cgi/query-pr.cgi?pr=150996 Thanks again for your input regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Le 12 nov. 2010 à 01:04, Olivier Mueller a écrit : Good evening, On Tue, 2010-06-22 at 10:45 +0200, Olivier Mueller wrote: Problem: [...@pandora ~]$ php -v -c /usr/local/etc/php.ini-production PHP 5.3.2 with Suhosin-Patch (cli) (built: Jun 14 2010 18:11:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) Here's what did it for me : remove the following lines from /usr/ports/textproc/libxml2/files/patch-configure and rebuild+reinstall libxml2 @@ -20678,6 +20679,8 @@ fi fi fi ;; + *freebsd*) THREAD_LIBS= + ;; esac if test $WITH_THREADS = 1 ; then THREAD_CFLAGS=$THREAD_CFLAGS -D_REENTRANT I found this somewhere but cannot remember the thread url unfortunately... NZ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [solved] Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Olivier Mueller ha scritto: Brillant! It fixed the issue, many thanks. This is not the correct fix, the correct fix is to enable threads in php, using the appropriate OPTION. -- Alex Dupre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Good evening, On Tue, 2010-06-22 at 10:45 +0200, Olivier Mueller wrote: Problem: [...@pandora ~]$ php -v -c /usr/local/etc/php.ini-production PHP 5.3.2 with Suhosin-Patch (cli) (built: Jun 14 2010 18:11:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) If I comment the line extension=imagick.so in /usr/local/etc/php/extensions.ini , it works fine (but without imagick then...). I tried recompiling about nearly all related packages (png, imagemagick, php, etc.), but it didn't helped. Same if I comment some other extensions (like pdf.so, etc.). All packages are 100% uptodate, as well as the OS (7.3-RELEASE-p1 amd64), but it was previously a 7.2 system, so this may have an influence. Is anybody using pecl-imagick without this segfault at the moment? Or do you have any suggestion about what I could try? I will setup a blank 7.3 system as a VM later this week to test by myself I finally did that now (vmware-based freebsd basic system + fresh ports tree + portinstall -rvbp php5 pecl-imagick), and it is exactly the same: Segfault still displayed. Maybe it's related to the WITHOUT_X11=yes in my make.conf ? I'll try again without that parameter later. Here are the ports list and gdb output, maybe someone will have an idea why it is reacting like that? : [r...@bsdbox73 ~]# php -v PHP 5.3.3 with Suhosin-Patch (cli) (built: Nov 11 2010 14:40:34) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) [r...@bsdbox73 ~]# [r...@bsdbox73 ~]# gdb php php.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.4 Reading symbols from /lib/libz.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.4 Reading symbols from /usr/local/lib/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x000803190820 in ?? () (gdb) (gdb) bt #0 0x000803190820 in ?? () #1 0x000800db17d5 in xmlFreeMutex () from /usr/local/lib/libxml2.so.5 #2 0x000800db1215 in xmlCleanupGlobals () from /usr/local/lib/libxml2.so.5 #3 0x000800d49d3a in xmlCleanupParser () from /usr/local/lib/libxml2.so.5 #4 0x0044ff28 in php_libxml_shutdown () #5 0x0044ff59 in zm_shutdown_libxml () #6 0x00558f2f in module_destructor () #7 0x0056061a in zend_hash_apply_deleter () #8 0x00560888 in zend_hash_graceful_reverse_destroy () #9 0x00554357 in zend_shutdown () #10 0x005005f5 in php_module_shutdown () #11 0x005dea4f in main () #12 0x004186de in _start () #13 0x000800781000 in ?? () #14 0x in ?? () #15 0x in ?? () [...] ---Type return to continue, or q return to quit---q Quit (gdb) [r...@bsdbox73 ~]# cat /etc//make.conf # om/20080318 WITHOUT_X11=yes [r...@bsdbox73 ~]# cat /usr/local/etc/php/extensions.ini extension=imagick.so [r...@bsdbox73 ~]# uname -a FreeBSD bsdbox73.omx.ch 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 05:25:24 UTC 2010 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 [r...@bsdbox73 ~]# pkg_info ImageMagick-nox11-6.6.4.10 Image processing tools apache-2.0.64 Version 2.0.x of Apache web server with prefork MPM. apr-0.9.19.0.9.19 Apache Portability Library autoconf-2.68 Automatically configure source code on many Un*x platforms autoconf-wrapper-20071109 Wrapper script for GNU autoconf automake-1.11.1 GNU Standards-compliant Makefile generator (1.11) automake-wrapper-20071109 Wrapper script for GNU automake bash-4.0.35 The GNU Project's Bourne Again SHell cups-client-1.4.4 Common UNIX Printing System: Library cups
Segmentation fault: 11 (core dumped)
r...@mx1 ~ 496$ csh Segmentation fault: 11 (core dumped) r...@mx1 ~ 497$ i even updated all my system to latest -RELEASE r...@mx1 ~ 499$ uname -a FreeBSD mx1.alexus.biz 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #3: Sun Mar 29 05:42:35 UTC 2009 ale...@dd.alexus.org:/usr/obj/usr/src/sys/GENERIC amd64 r...@mx1 ~ 500$ I've had that on other systems as well, this isn't the first one I'm having this issue... -- http://alexus.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault: 11 (core dumped)
On Mon, Apr 6, 2009 at 3:03 PM, alexus ale...@gmail.com wrote: r...@mx1 ~ 496$ csh Segmentation fault: 11 (core dumped) r...@mx1 ~ 497$ Segmentation Fault 11 is typically indicative of hardware failure (CPU, RAM, motherboard). Can you run memtest86+ and test that theory? -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Segmentation fault: 11 (core dumped)
On Mon, Apr 6, 2009 at 3:09 PM, Glen Barber glen.j.bar...@gmail.com wrote: On Mon, Apr 6, 2009 at 3:03 PM, alexus ale...@gmail.com wrote: r...@mx1 ~ 496$ csh Segmentation fault: 11 (core dumped) r...@mx1 ~ 497$ Segmentation Fault 11 is typically indicative of hardware failure (CPU, RAM, motherboard). Can you run memtest86+ and test that theory? I doubt that it has anything to do with hardware, as a) everything else works fine except for this thing b) i'm getting same type of behavior on multiple systems (some of these systems are high end boxes, some of them are low end) -- Glen Barber -- http://alexus.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
PHP 5.2.8 crash (segmentation fault 11)
Hi all:
Freshly compiled PHP 5.2.8 with PECL and PHP5-extensions support
on FreeBSD 7.1 (i386) seems to be crashing in
#0 0x28e3e006 in hash_lookup (hashtab=0x29ea2f70,
key=0xbfbfea30 \221??\222)??{\206)p/??)??\r\226)`Qp() at misc.c:349
349 for (ret = hashtab-table[hash_index (hashtab,key)]; ret; ret =
ret-next)
[New Thread 0x28759400 (LWP 100083)]
The stack frame are shown below.
(gdb) bt
#0 0x28e3e006 in hash_lookup (hashtab=0x29ea2f70,
key=0xbfbfea30 \221??\222)??{\206)p/??)??\r\226)`Qp() at misc.c:349
#1 0x29867dae in find_alias () from /usr/local/lib/librecode.so.3
#2 0x29869361 in recode_new_outer () from /usr/local/lib/librecode.so.3
#3 0x2981dd6e in zm_startup_recode ()
from /usr/local/lib/php/20060613-debug/recode.so
#4 0x081c0f65 in zend_startup_module_ex (module=0x287cd100)
at /usr/ports/lang/php5/work/php-5.2.8/Zend/zend_API.c:1472
#5 0x081c81d2 in zend_hash_apply (ht=0x82f0a80,
apply_func=0x81c0dc0 zend_startup_module_ex)
at /usr/ports/lang/php5/work/php-5.2.8/Zend/zend_hash.c:673
#6 0x081c112f in zend_startup_modules ()
at /usr/ports/lang/php5/work/php-5.2.8/Zend/zend_API.c:1519
#7 0x08166db8 in php_module_startup (sf=0x82ec200, additional_modules=0x0,
num_additional_modules=0)
at /usr/ports/lang/php5/work/php-5.2.8/main/main.c:1843
#8 0x0823abf1 in php_cli_startup (sapi_module=0x82ec200)
at /usr/ports/lang/php5/work/php-5.2.8/sapi/cli/php_cli.c:357
#9 0x0823b8a6 in main (argc=2, argv=0xbfbfeda8)
at /usr/ports/lang/php5/work/php-5.2.8/sapi/cli/php_cli.c:716
Anybody pointers as to how to solve this issue ?
thanks
Saifi.___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PHP 5.2.8 crash (segmentation fault 11)
Saifi Khan wrote:
Hi all:
Freshly compiled PHP 5.2.8 with PECL and PHP5-extensions support
on FreeBSD 7.1 (i386) seems to be crashing in
#0 0x28e3e006 in hash_lookup (hashtab=0x29ea2f70,
key=0xbfbfea30 \221Û\222)À{\206)p/ê)ì\r\226)`Qp() at misc.c:349
349 for (ret = hashtab-table[hash_index (hashtab,key)]; ret; ret =
ret-next)
[New Thread 0x28759400 (LWP 100083)]
The stack frame are shown below.
snip
Anybody pointers as to how to solve this issue ?
Isn't this simply the classic problem with the order of the extensions
in extensions.ini?
http://www.pingle.org/2006/10
/Morgan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
segmentation fault 11
I saw a reference that linux.ko and kqemu.ko can start a segmentation fault 11. My memory is set to 2G in the loader file and physical is 1.77G. Would this cause the problem? _ See how Windows Mobile brings your life together—at home, work, or on the go. http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Segmentation fault (11)
This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Segmentation fault (11)
This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter __ Yahoo! Mail for Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (11)
At 05:48 PM 7/27/2005, steve lasiter wrote: This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. I believe that 5.x versions of MySQL are still considered to be beta quality at best. It might be a good idea to use 4.1 which is their recommended version. -Glenn The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter __ Yahoo! Mail for Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (11)
do you have a copy of the core dump? also sometimes when you use php to interpret the page via the shell it leaves a little extra useful info. since it's a fault and not a kernel panic i wouldnt be worried that its freebsd itself fucking things up. this error only comes up when a program accesses a memory location that it wasn't assigned to. Because of error I've reinstalled Apache 1.3 and Perl5. what was the error and how was php5 compiled? did you uninstall php4 or did you do a FORCE_PKG_REGISTER? when you say that other php sites work fine do you mean that other php scripts work fine on your apache server? I apologize but your info is pretty general. all i can suggest is do a full deinstall clean on apache+php5 and php4 if the memory glitch has to do with its compilation. perhaps if you email the debug log specifics (strace php webpage.php) we could understand where the program is at when it crashes. -Ben steve lasiter wrote: This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Segmentation fault (11)
i seem to use mysql 5.02 just fine even with a few unsuggested code tweaking on my leet 366Mhz cyrix based e-machine :-P thats why i was looking toward a different direction. hopefully you'll solve the situation. -Ben steve lasiter wrote: This is a questions to the group since I'm not sure if it's related to my FreeBSD 5.4 OS or something else. I'm on a Dell Pentium 2.55Ghz with 1 GB Ram. Background: In trying to install oscommerce I have uninstalled my php5 and went to php4. Because of error I've reinstalled Apache 1.3 and Perl5. My database is MySQL 5.02. The problem: when I attempt to open an index.php file in the oscommerce program I get, in my httpd-error.log [notice] child pid xxx exit signal Segmentation fault(11) All other php related sites are functioning well with no problems. Do you believe this is being caused by the code in the oscommerce program or something FreeBSD is doing? Thanks for input Dean Lasiter __ Yahoo! Mail for Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
