Subject: dmalloc useless?

From: Dominik Vogt <[email-masked]>
Date: Sat, 1 Jan 2000 06:20:01 +0100

Paul (PDS), I've tried to use dmalloc with fvwm but ran
into several problems that make dmalloc useless for us
if they can't be solved:

 1) All modules and fvwm itself dump their log into the
    same file.  The last one to exit wins.  This can be
    circumvented by compiling everything w/o dmalloc,
    then reconfiguring and compiling fvwm or the specific
    module with dmalloc.
    [inconvenient but no show stopper]

 2) modules/FvwmGtk/menu.c can't be compiled with dmalloc
    because the dmalloc header does something bad with a
    macro 'FREE' that seems to be used in g_free.
    [can be circumvented by removing g_free() from the file]

 3) Virtually all memory allocations are reported from
    safemalloc.c :-(  A stack trace is needed to make this
    information usable!
    [very serious problem]

 4) dmalloc reports *thousands* blocks of unfreed memory
    when fvwm exits.  This makes leak detection nigh
    impossible.

Any ideas how to solve these problems (don't care about
1 or 2 unless 3 and 4 are solved)?

Bye

Dominik ^_^

--
Dominik Vogt, [email-masked]
Reply-To: [email-masked]
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [email-masked].
To report problems, send mail to [email-masked]