Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11606
Return-Path: <curt@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 16671 invoked by uid 1010); 29 Jul 2004 04:20:14 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 16637 invoked from network); 29 Jul 2004 04:20:13 -0000
Received: from unknown (HELO took.shire) (68.122.184.4)
  by pb1.pair.com with SMTP; 29 Jul 2004 04:20:13 -0000
Received: (qmail 68348 invoked by uid 1001); 29 Jul 2004 04:35:10 -0000
Date: Thu, 29 Jul 2004 04:35:10 +0000
To: internals@lists.php.net
Message-ID: <20040729043510.GH6522@bagend.shire>
Mail-Followup-To: internals@lists.php.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: Memory leak debugging
From: curt@php.net (Curt Zirzow)

Is there prefered/suggested method on debugging memory leaks?

For example:

  $i = 100;
  while($i-- ) {
      list($foo['a']) = array('bar');
  }

Results with:

Zend/zend_execute.c(3383) :  Freeing 0x0840E1CC (4 bytes),
script=t.php
Zend/zend_variables.c(137) : Actual location (location was relayed)
Last leak repeated 99 times
Zend/zend_execute.c(3380) :  Freeing 0x0840E188 (16 bytes),
script=t.php
Last leak repeated 99 times
=== Total 200 memory leaks detected ===





Curt
-- 
First, let me assure you that this is not one of those shady pyramid schemes
you've been hearing about.  No, sir.  Our model is the trapezoid!