Re: mtrace reading

>Thanks for replies,
>I have tried 'memprof' but there are problems (I suppose) for programs th=
>use g_spawn.
>> mtrace appl appl_log
>I get 'No memory leaks.' Mah?!? I hope (but I'm not sure) that my prg wor=

unless i'm forgetting something, and mtrace *is* a valgrind "skin",
then you should be using valgrind, which is the memory tool to beat
all memory tools. valgrind is the bomb. a large, friendly, helpful

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]