ID: 28578 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Assigned +Status: Closed Bug Type: Unknown/Other Function Operating System: win PHP Version: 5CVS-2004-05-30 (dev) Assigned To: john New Comment:
Edin has updated the libtidy and the problem is solved. Many thanks! Previous Comments: ------------------------------------------------------------------------ [2004-06-24 19:02:51] [EMAIL PROTECTED] I've found this is a libtidy problem! More info at: https://sourceforge.net/tracker/index.php?func=detail&aid=964946&group_id=27659&atid=390963 The problem is that the windows binnaries use a old version of libtidy and still contain that error. Maybe its time to update this lib (it compiles in 5 minutes...) ------------------------------------------------------------------------ [2004-05-31 15:16:33] [EMAIL PROTECTED] I've built PHP with latest tidy lib on cygwin and it doesn't segfault. The problem can be in the libTidy itself, as the binaries provided by the snaps machine use a very old version of the libTidy. ------------------------------------------------------------------------ [2004-05-31 12:17:41] [EMAIL PROTECTED] Works for me on linux, assigning to the maintainer. ------------------------------------------------------------------------ [2004-05-30 22:36:58] jed at jed dot bz Heh, sorry. That would be 0xC0000005. ------------------------------------------------------------------------ [2004-05-30 22:35:07] jed at jed dot bz PHP 5.0.0RC2. Run via CLI. I was able to reproduce this bug. My gut feeling, which I will check after I submit this debug info (I have the debugger attached at present), is that <?php ?> will parse correctly. Unhandled exception in php.exe (PHP_TIDY.DLL): 0xC00000005: Access Violation. Unfortunately, I do not have the debug build of PHP. Best I can offer you is this: PHP_TIDY! 00ab93fe() That's my call stack. Sorry. I'll get the debug version of PHP and recheck this later, if I remember. Rechecking my initial gut suspicion, this piece of code works fine. $tidy = tidy_parse_string('<?php ?>'); My advice at present is to not use short tags in tidy-parsed code, as tidy's logic probably does not recognize <? ?> and attempts to parse it. However, a worthy problem for looking into. ------------------------------------------------------------------------ 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/28578 -- Edit this bug report at http://bugs.php.net/?id=28578&edit=1
