Justtechjobs.com Find a programming school near you






Online Campus Both


php3-list | 199901

Re: [PHP3] Debugging messages From: Rasmus Lerdorf (rasmus <email protected>)
Date: 01/31/99

> Freeing 80d1ff8 (22 bytes), allocated in functions/pgsql.c on line 861
> Freeing 80d1ed0 (15 bytes), allocated in functions/pgsql.c on line 861
> Freeing 80d1dc8 (2 bytes), allocated in functions/pgsql.c on line 861
>
> Does anybody at PHP need to know about this stuff, or is it it as
> innoccuous as it seems? Guess I've gotten out of the habit of freeing
> my pg_results. Bad boy! :-(

Even if you don't free your results, PHP should be doing it without those
error messages. PHP has a two-stage safety net here. The first is the
one that cleans up after guys like you in user-space. Like when you
forget to free your result sets and stuff. That's fine. But, the second
safety net is an internal one that cleans up when the people who write the
internal PHP code screw up. The above messages give us an indication that
somebody is forgetting to free something under certain circumstances in
the pgsql module. Since the safety net is catching it no memory is
actually leaked but it should still be fixed. If you really want to help
you could try to come up with the shortest possible script that generates
those warnings and send it to php-dev <email protected> and we should be able
to track it down.

-Rasmus 

--
PHP 3 Mailing List   http://www.php.net/
To unsubscribe send an empty message to php3-unsubscribe <email protected>
To subscribe to the digest list:  php3-digest-subscribe <email protected>
For help: php3-help <email protected>  Archive:  http://www.php.net/mailsearch.php3
List administrator:  zeev-list-admin <email protected>