#18953 [Com]: T_INLINE_HTML parser error
| From: | ddreier at mbuti dot org | Date: | Mon, 19 Aug 2002 19:38:39 +0000 |
| Subject: | #18953 [Com]: T_INLINE_HTML parser error | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-17227@lists.php.net to get a copy of this message | ||
ID: 18953
Comment by: ddreier@mbuti.org
Reported By: fclever@verinform.com
Status: Open
Bug Type: Scripting Engine problem
Operating System: Win32
PHP Version: 4.2.2
New Comment:
I have run into the same problem, running the same extensions, under
Windows NT 4. It is a fairly significant issue for me.
Previous Comments:
------------------------------------------------------------------------
[2002-08-19 14:44:31] fclever@verinform.com
The latest 4.3.0-dev snapshot crashes very frequently.
The latest STABLE snapshot (4.2.3-dev) performs significantly more
stable.
------------------------------------------------------------------------
[2002-08-17 04:39:26] edink@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php4-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-latest.zip
------------------------------------------------------------------------
[2002-08-17 01:22:43] fclever@verinform.com
mistyped email.
------------------------------------------------------------------------
[2002-08-17 00:29:53] fclever@verinfom.com
It occurs on Windows N% 4.0 SP 6 and Windows 2000 SP2.
The following extensions are enabled:
- OCI8
- GD 2
- XSLT (Sablot)
- Session
This seems to happen primarly with scripts that are heavily Object
Oriented. It does not seem to be load related.
thanks.
------------------------------------------------------------------------
[2002-08-16 23:33:59] kalowsky@php.net
Theres certainly a lot of Win32 machines out there, think you can
narrow it down a bit?
Also, can you tell us what (if any) extensions for PHP you're running
(session, ODBC, mbstring, etc etc) ?
------------------------------------------------------------------------
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/18953
--
Edit this bug report at http://bugs.php.net/?id=18953&edit=1