finding memory leaks
- From: Jim Edwards <jimedwards altavista com>
- To: gtk <gtk-list gnome org>
- Subject: finding memory leaks
- Date: Tue, 18 Sep 2001 11:37:17 +0000
Hi,
I´m trying to chase memory leaks in a farily large program. I´ve tried
memprof but for whatever reason it doesn´t work, so I´m using mtrace.
The output from mtrace gives me a whole list of memory not freed but
it often only gives me an address for the caller. I assume these are
malloc calls from glib (Is this a good assumption?) The question is
how do I compile and link glib and/or gtk to get the source location of
the caller rather than
just the address?
I see in the configure for glib are some flags --enable-mem-check,
--enable-mem-profile can anyone tell me what these do and wether the
can help?
Thanks,
Jim
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]