ID: 24792
Updated by: [email][/email]
Reported By: tilman dot giese at gmx dot de
-Status: Assigned
+Status: Closed
Bug Type: mbstring related
Operating System: Linux
PHP Version: 4.3.2
Assigned To: fujimoto
New Comment:

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at [url][/url].

In case this was a doentation problem, the fix will show up soon at

In case this was a website problem, the change will show
up on the site and on the mirror sites in short time.

Thank you for the report, and for helping us make PHP better.

Previous Comments:

[2003-07-25 11:06:16] tilman dot giese at gmx dot de

I am not sure, but after experimenting a bit, it seems that all scripts
are already finished when the segfault occurs. Unfortunately, there is
no free debugger for Linux that provides debugging of remote
connections and that makes it very complicated. I tried and the trace files are complete and closed (the only
difference is that sometimes another segfault occurs in an vfprintf
call - but I assume that this can be closely related to my problem
since php tries to free the memory and apd tries to print the memory
(that is not allocated any more - I suppose)).


[2003-07-25 05:33:37] tilman dot giese at gmx dot de

As the segmentation fault only appears sporadically, it is not that
easy to find out which code can cause it. But I will try my very best
and inform you if I know anything. Meanwhile I compiled PHP with
debugging support and got the following gdb output:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 114696 (LWP 28332)]
0x406d752f in _efree (ptr=0x2a, __zend_filename=0x407380de
"Zend/zend_language_scanner.c", __zend_lineno=2870,
__zend_orig_filename=0x0, __zend_orig_lineno=0) at
(gdb) bt
#0 0x406d752f in _efree (ptr=0x2a, __zend_filename=0x407380de
"Zend/zend_language_scanner.c", __zend_lineno=2870,
__zend_orig_filename=0x0, __zend_orig_lineno=0) at
#1 0x406c816c in shutdown_scanner (tsrm_ls=0x83a3608) at
#2 0x406edc57 in zend_deactivate (tsrm_ls=0x83a3608) at
#3 0x406a97c8 in php_request_shutdown (dummy=0x0) at
#4 0x407083ba in php_apache_request_dtor (r=0x8496100,
at /tmp/php-4.3.3RC1/sapi/apache2handler/sapi_apache2.c:445
#5 0x40708769 in php_handler (r=0x8496100) at
#6 0x0806b6d8 in ap_run_handler ()
#7 0x0806bde9 in ap_invoke_handler ()
#8 0x08065e09 in ap_process_request ()
#9 0x08060afe in _start ()
#10 0x08076748 in ap_run_process_connection ()
#11 0x08076afe in ap_process_connection ()
#12 0x0806764f in ap_graceful_stop_signalled ()
#13 0x08067f15 in ap_graceful_stop_signalled ()
#14 0x402c06c6 in dummy_worker (opaque=0x2) at thread.c:127
#15 0x4033bd80 in pthread_start_thread () from /lib/
#16 0x4033be7e in pthread_start_thread_event () from


[2003-07-24 13:56:29] [email][/email]

That is a possibility, besides phpMyAdmin do you have another other
preferably much smaller scripts that could be used to te the


[2003-07-24 12:47:57] tilman dot giese at gmx dot de

After having compiled PHP about a hundred times, I found out that using
--enable-zend-multibyte causes the segmentation fault. Is the Zend
Multibyte Support thread safe?


[2003-07-24 09:24:14] [email][/email]

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the doentation available at
[url][/url] and the instructions on how to report
a bug at [url][/url]

Your phpinfo() does not reflect the configure line you have used. So it
does not appear you are using PHP you've compiled.

If you are only using PHP + MySQL then php should be thread safe,
however I still recommend to explicitly enable


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

Edit this bug report at [url][/url]