# Results of running the entire testsuite with valgrind

- Thread: https://externals.io/message/44389
- Original archive: https://news-web.php.net/php.internals/44389
- Started by Gwynne Raskind on 2009-06-21T10:50:35+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #44389 — Gwynne Raskind — 2009-06-21T10:50:35+00:00

URL: https://externals.io/message/44389#44389

I ran the entire PHP testsuite (as compiled on my system) under  
valgrind for Darwin and came up with quite a mess of leaks and a  
couple of crashes.

The results file is quite ginormous, so I uploaded it to my site for  
the morbidly curious to have a look at:

http://darkrainfall.org/php_test_results_valgrind.txt

Some caveats about these results:

- Darwin's valgrind doesn't support the `symlink()` syscall, so all  
tests using `symlink()` broke.

- I didn't provide the proper environment variables for MySQL to  
connect, so all those tests broke too.

- There seem to be several valgrind-caught bugs in OpenSSL 0.9.8k that  
aren't caught by valgrind's suppression files or OpenSSL's PURIFY  
flag, so you'll have to wade through those pointless warnings.

- Two tests crashed HARD when run (with or without valgrind):

ext/standard/tests/strings/str_pad_variation5.phpt (SIGBUS on `NULL`  
pointer)
tests/output/ob_011.mem (SIGSEGV on unmapped non-NULL pointer)

-- Gwynne