#17802 [Fbk->NoF]: php dumps core with ingres extension, not without

ID: 17802 Updated by: sniper@php.net Reported By: H.F.Schouten@hhs.nl -Status: Feedback +Status: No Feedback Bug Type: Reproducible crash Operating System: Solaris 2.7 PHP Version: 4.2.1 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2002-06-17 15:56:46] sniper@php.net Does it crash if you compile the Ingres extension as static? And to generate a useful backtrace, you have to compile PHP with --enable-debug too. Otherwise the trace is useless. (to get backtrace, use 'bt' btw..) --Jani ------------------------------------------------------------------------ [2002-06-17 11:18:01] H.F.Schouten@hhs.nl I have build php-4.2.1 with configure as follows: ./configure --prefix=/test/php-4.2.1 --with-config-file-path=/test/php-4.2.1 --with-mysql=/test/mysql --with-ingres=shared,/usr/local/OI/ingres --enable-trans-sid When I add in php.ini the line extension=ingres_ii.so, the command php dumps core after giving EOF as thus: prompt> php ^D X-Powered-By: PHP/4.2.1 Content-type: text/html Segmentation Fault (core dumped) prompt> Running a php-script with ingres commands works fine, but also ends with a core dump. Without the ingres extension line no core is dumped... gdb gives the following backtrace: (gdb) where #0 0xfef8ff74 in ?? () #1 0xff1d6840 in keys_destruct () from /usr/lib/libc.so.1 #2 0xff1a03e0 in _exithandle () from /usr/lib/libc.so.1 #3 0xff21a194 in exit () from /usr/lib/libc.so.1 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17802&edit=1