ID: 37349
Updated by: nlopess@php.net
Reported By: nlopess@php.net
-Status: Feedback
+Status: Open
Bug Type: Streams related
Operating System: n/a
PHP Version: 6CVS-2006-05-07 (CVS)
Assigned To: pollita
New Comment:
I've upgraded ICU to version 3.4.1 and I still get the same problems:
http://mega.ist.utl.pt/~ncpl/php6-tidy-valgrind.txt
Previous Comments:
------------------------------------------------------------------------
[2006-05-27 09:40:35] nlopess@php.net
no, Tony, I'm not :)
I'll update ICU to check if that is the problem.
------------------------------------------------------------------------
[2006-05-27 09:33:51] tony2001@php.net
Nuno, you must be kidding:
-----
[24 May 9:53pm UTC] tony2001@php.net
<..>
I can't reproduce it with the latest CVS.
-----
I said I don't see any valgrind warnings with any of tidy tests, what's
the point to refer to your first post?
What exactly do you get?
------------------------------------------------------------------------
[2006-05-26 18:03:44] nlopess@php.net
Tony: its in my first comment :)
You just need to run valgrind on run-tests.php while testing the
tidy/tests/020.phpt file. This produces a nice error message: 'BORK
TEST', along with a huge valgrind report. (also, the problem might be
in ICU. I haven't look further though)
------------------------------------------------------------------------
[2006-05-26 06:38:27] tony2001@php.net
Okay, but how to reproduce it?
------------------------------------------------------------------------
[2006-05-25 17:06:08] nlopess@php.net
yep, it is still valid. This bug has nothing to do with tidy itself. It
happens that I made a test for tidy that triggered a problem somewhere
else.
------------------------------------------------------------------------
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/37349--
Edit this bug report at http://bugs.php.net/?id=37349&edit=1