Bug #17786 Updated: Coredump on \\0 backref (011.phpt)

From: Date: Mon, 17 Jun 2002 22:57:25 +0000
Subject: Bug #17786 Updated: Coredump on \\0 backref (011.phpt)
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-10963@lists.php.net to get a copy of this message
ID: 17786 Updated by: sniper@php.net Reported By: msopacua@idg.nl -Status: Duplicate +Status: Closed Bug Type: Regexps related Operating System: BSD/OS 4.2 PHP Version: 4.0CVS-2002-06-16 New Comment: This bug has been fixed in CVS. You can grab a snapshot of the CVS version at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites. Thank you for the report, and for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2002-06-16 15:26:07] msopacua@idg.nl Ok: 1) How did you find it - oh you posted it. I tried \0 in ALL categories and it didn't yield any results. Searching the database needs improvement. 2) I did compile with --enable-debug and I gave a backtrace. ------------------------------------------------------------------------ [2002-06-16 15:19:10] sander@php.net Dupe of #15829. Please compile PHP with --enable-debug and provide a backtrace and post it on #15829. ------------------------------------------------------------------------ [2002-06-16 12:41:47] msopacua@idg.nl Nope, no regex config flag at all. So the php default is used. Oh - and since it forks off another CLI executable, I can't get to that one in gdb - tried 'set follow-fork-mode ask', but doesn't help a bit. ------------------------------------------------------------------------ [2002-06-16 12:27:28] rasmus@php.net Did you compile using --with-regex=system? That is known to be broken on some platforms. ------------------------------------------------------------------------ [2002-06-16 12:25:00] msopacua@idg.nl Heck - this is even more complicated. If I take the 'FILE' section in 011.phpt and put it in 011.php, then use: $ /chroot/home/mdev/php4-200206160300/sapi/cli/php -e -f ./011.php abcdef123ghi all is fine. With make test it failes. The output of gdb is complete, just in case, here it is again: ---Type <return> to continue, or q <return> to quit--- #0 0x486b660f in memcpy () from /shlib/libc.so.2 (gdb) bt #0 0x486b660f in memcpy () from /shlib/libc.so.2 #1 0x814ed64 in ?? () #2 0x814f375 in ?? () #3 0x814f4c0 in ?? () #4 0x81c473a in ?? () #5 0x81b3d1b in ?? () #6 0x81851f1 in ?? () #7 0x81c9fdb in ?? () #8 0x806d8ce in ?? () (gdb) I've also topped make test while running, to see if I go through any shell limits, but php doesn't even go above 5 Megs and I can take 384 Meg in this shell. ------------------------------------------------------------------------ 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/17786 -- Edit this bug report at http://bugs.php.net/?id=17786&edit=1

« previous php.bugs (#10963) next »