Bug #18528 Updated: Php crashes upon using eregi_replace

ID: 18528 Updated by: flash@daaw.org Reported By: flash@daaw.org -Status: Feedback +Status: Open Bug Type: Reproducible crash Operating System: Redhat linux 7.1 (kernel 2.4.18) PHP Version: 4.2.2 New Comment: Its already in here in the initial bugreport. Previous Comments: ------------------------------------------------------------------------ [2002-07-24 19:32:30] sniper@php.net Please provide a complete, self-contained but short example script which can be used to reproduce this.. ------------------------------------------------------------------------ [2002-07-24 04:58:25] flash@daaw.org rebuild, retried still not working. ------------------------------------------------------------------------ [2002-07-24 04:49:58] derick@php.net I think you mean "I used the same configure OPTIONS" as in PHP 4.2.1. Please try to rebuild the configure script like I asked. Derick ------------------------------------------------------------------------ [2002-07-24 04:36:54] flash@daaw.org I used the same configure script as with version 4.2.1 and I just now went back again to 4.2.1 and the problem is gone again. here are my configure options: ./configure --with-apxs=/usr/local/apache/bin/apxs \ --with-config-file-path=/usr/local/apache/conf \ --with-mysql=/usr/local \ --with-gd \ --with-system-regex I will retry in a minute with the options as you said. ------------------------------------------------------------------------ [2002-07-24 04:32:23] derick@php.net That doesn't make much sense, as 4.2.2 is exactly the same as 4.2.1 + the security fix and a new configure script. I suspect the problem lies in the configure script used. If you have autoconf 2.52 isntalled (check with autoconf --version) then you can try this: cd php-4.2.2 rm configure ./cvsclean ./buildconf ./configure --your options make If this doesn't solve it, you can try try to add --with-regex=system to your configure options. Derick ------------------------------------------------------------------------ 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 http://bugs.php.net/18528 -- Edit this bug report at http://bugs.php.net/?id=18528&edit=1