Bug #18528 Updated: Php crashes upon using eregi_replace

ID: 18528 Updated by: sniper@php.net Reported By: flash@daaw.org -Status: Open +Status: Feedback -Bug Type: Reproducible crash +Bug Type: Regexps related Operating System: Redhat linux 7.1 (kernel 2.4.18) PHP Version: 4.2.2 New Comment: Didn't I ask just trying it on the command line? ie. ./configure and then use the NOT INSTALLED binary to run your test script.. Previous Comments: ------------------------------------------------------------------------ [2002-07-25 08:24:00] flash@daaw.org first of all, im not a production server and am not interested in running dev versions on that. second I present a bug in php 4.2.2 and that doesnt mean the bug is in 4.3 ------------------------------------------------------------------------ [2002-07-25 08:12:40] sniper@php.net Hmm..I tested with the 4.3.0-dev actually..can you try this snapshot: http://snaps.php.net/php4-latest.tar.gz Just try it on command line.. ------------------------------------------------------------------------ [2002-07-25 08:08:39] flash@daaw.org I have done this yesterday already, lemme tell you exactly what I did first. I upgraded from php 4.2.1 to 4.2.2 using the configure script as stated above (so using the system regex) that didnt work next I installed php 4.2.2 (from a new tarball) without the system regex and it gave exactly thesame problem. this morning I removed apache and php completely, I extraced new tarballs from both and installed without system regex and I still get thesame problem with all eregi commands. ------------------------------------------------------------------------ [2002-07-25 07:50:39] sniper@php.net Just that you know, I don't get any crash with that script.. ------------------------------------------------------------------------ [2002-07-25 07:50:16] sniper@php.net Please try a clean build (from freshly extracted sources) and DO NOT use system regex.. ------------------------------------------------------------------------ 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