Hey everybody,
I've been messing around a little bit with the new development tools
in Leopard. If I've managed to use the memory leak tool properly
(based on Dtrace, with a GUI), and do in fact understand what I'm
doing, you should find that the logic of the following functions
allows a return without deallocating allocated memory, i.e., they can
(and sometimes do) leak.
If this proves to be correct, and useful, then I'll do further testing.
The format is [frame number] [library] [function].
Two sixteen byte leaks:
0 libSystem.B.dylib malloc
1 libglib-1.2.0.dylib g_malloc
2 gtk-gnutella prop_get_guint32
3 gtk-gnutella update_entry_duration
4 gtk-gnutella settings_gui_init
5 gtk-gnutella main_gui_init
6 gtk-gnutella main
7 gtk-gnutella start
8 0x0
One sixteen byte leak:
0 libSystem.B.dylib malloc
1 libglib-1.2.0.dylib g_malloc
2 gtk-gnutella prop_get_guint64
3 gtk-gnutella update_size_entry
4 gtk-gnutella settings_gui_init
5 gtk-gnutella main_gui_init
6 gtk-gnutella main
7 gtk-gnutella start
8 0x0
Four sixteen byte leaks:
0 libSystem.B.dylib calloc
1 libglib-1.2.0.dylib g_malloc0
2 gtk-gnutella filter_new_text_rule
3 gtk-gnutella xml_to_text_rule
4 gtk-gnutella xml_to_filter
5 gtk-gnutella search_retrieve_xml
6 gtk-gnutella search_gui_common_init
7 gtk-gnutella main_gui_init
8 gtk-gnutella main
9 gtk-gnutella start
10 0x0
regards,
Matt
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
gtk-gnutella-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
