ID: 27011
User updated by: ehicks at binarymagi dot com
Reported By: ehicks at binarymagi dot com
-Status: Feedback
+Status: Open
Bug Type: PCRE related
Operating System: Solaris 9
PHP Version: 4CVS-2004-01-23
New Comment:
Yeah.
[EMAIL PROTECTED] cli]# ./php < crashphp.php
Bus Error (core dumped)
That's using:
CFLAGS=-DNO_RECURSE ./configure --disable-all --disable-cgi
--with-pcre-regex
No idea what it's problem is. I can run more gdb tests on the core
dump if you want.
Previous Comments:
------------------------------------------------------------------------
[2004-01-26 23:13:21] [EMAIL PROTECTED]
Did you try with the configure line I gave?
(don't forget also doing 'make clean' before 'make', I forgot that from
it :)
------------------------------------------------------------------------
[2004-01-26 23:10:52] ehicks at binarymagi dot com
Adding -DNO_RECURSE to PHP's compile didn't help either.
------------------------------------------------------------------------
[2004-01-26 22:23:20] ehicks at binarymagi dot com
Actually, it is. That configure line has been updated since I posted
it. ldd shows that the new module is indeed using the libpcre from
/usr/local/lib.
I added the no_recurse to the PCRE build, though, not PHP. That's why
I asked. I will try it in PHP and see what happens.
------------------------------------------------------------------------
[2004-01-26 21:38:41] [EMAIL PROTECTED]
You're missing the point: PHP is NOT using your external build PCRE
lib! (given your configure line you added in your report)
Try this for PHP:
# rm config.cache ; CFLAGS=-DNO_RECURSE ./configure --disable-all
--disable-cgi --with-pcre-regex && make
Then try your script with the sapi/cli/php
------------------------------------------------------------------------
[2004-01-26 20:44:27] ehicks at binarymagi dot com
Added -DNO_RECURSE to PCRE's CFLAGS and it's still no-go. Same
segfault, same gdb backtrace. You did mean to put no_recurse into the
PCRE compile and not the PHP compile, right? Very frusterated, I
managed to bypass the feature of IMP that was causing the problem so
it's no longer inhibiting my progress. (It'd still be nice to get it
working, though.)
------------------------------------------------------------------------
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/27011
--
Edit this bug report at http://bugs.php.net/?id=27011&edit=1