On Sun, Aug 06, 2006 at 09:45:00AM +0200, Iago Rubio wrote: > > I've just compiled and run this code snippet with valgrind, and the > results are on my system (Fedora): > > ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 12 from 1) > malloc/free: in use at exit: 0 bytes in 0 blocks. > malloc/free: 30 allocs, 30 frees, 1,981 bytes allocated.
1981 bytes allocated?! What is the part you are not telling us? Taking stock Fedora Core 5 installation (updated) and compling just /* Avoid preprocessed size talks */ void g_type_init(void); int main(void) { g_type_init(); return 0; } with gcc -o simple simple.c -lgobject-2.0 I get numbers like: x86_64: malloc/free: 413 allocs, 194 frees, 376,464 bytes allocated. i386: malloc/free: 415 allocs, 194 frees, 192,000 bytes allocated. So please enlighten me how you achieve only 1981 bytes allocated by a complete Gtk+ program on Fedora. (There are a few tricks I can imagine, but they generally render the specification `Gtk+' or `Fedora' irrelevant, modify valgrind behaviour, make the compiler to build a different program, etc.) Yeti -- Anonyms eat their boogers. _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list