#37349 [Asn->Fbk]: memory corruption within run-tests.php

From: Date: Sat, 27 May 2006 09:33:51 +0000
Subject: #37349 [Asn->Fbk]: memory corruption within run-tests.php
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-97672@lists.php.net to get a copy of this message
 ID:               37349
 Updated by:       tony2001@php.net
 Reported By:      nlopess@php.net
-Status:           Assigned
+Status:           Feedback
 Bug Type:         Streams related
 Operating System: n/a
 PHP Version:      6CVS-2006-05-07 (CVS)
 Assigned To:      pollita
 New Comment:

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?


Previous Comments:
------------------------------------------------------------------------

[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.

------------------------------------------------------------------------

[2006-05-24 21:53:47] tony2001@php.net

Is this still valid?
I can't reproduce it with the latest CVS.

------------------------------------------------------------------------

[2006-05-07 22:24:04] nlopess@php.net

Maybe Sara is the best person to look into this (as she implemented the
Unicode streams stuff).

------------------------------------------------------------------------

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


Thread (14 messages)

« previous php.bugs (#97672) next »