News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Derick Rethans' Blog:
Valgrinding shared modules
August 08, 2011 @ 14:35:20

In the process of some development he's been doing on various shared modules for PHP, Derick Rethans stumbled across an issue with using Valgrind to test his code:

While testing whether I correctly free all memory with Valgrind, I ran into the issue where I couldn't see the stack frames of where the memory leaks occurred in the extensions, and once I even ran into a Valgrind bug. The reason why Valgrind could not show the function names belonging to the stack frames is because PHP had already unloaded the shared extensions from memory.

A work-around he found was compiling the modules, but he wanted something "more correct" and less of a hassle. As a result he added a check for the ZEND_DONT_UNLOAD_MODULES environment flag to the PHP core to handles this case specifically. He includes a snippet of example code showing the Valgrind results with and without the flag.

0 comments voice your opinion now!
valgrind memory flag unload extension patch


blog comments powered by Disqus

Similar Posts

Vinu Thomas' Blog: PHP and Serial Ports

Jacob Santos' Blog: On PHP 5 Adoption

Christopher Jones' Blog: Casting PL/SQL arrays as REF CURSORS for Ruby (and PHP)

DevShed: A Quick Overview of the XML DOM Extension in PHP 5

Cyberlot's Blog: PHP Extension creating, the quick and dirty.


Community Events





Don't see your event here?
Let us know!


security artisanfiles podcast composer symfony opinion framework release version introduction community series language list laravel conference library tool interview voicesoftheelephpant

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework