17 Nov
2004
17 Nov
'04
8 p.m.
Hi Andrei,
never tried the combination of DBG_QM_MALLOC with free(0). I saw that
with F_MALLOC it have no side effects, but looks like it's a particular
case. Thanks for the clarifications.
Best regards,
Marian
Andrei Pelinescu-Onciul wrote:
On Nov 17, 2004 at 18:24, Marian Dumitru
<marian.dumitru(a)voice-sistem.ro> wrote:
--
Voice Sistem
http://www.voice-sistem.ro
Hi Paul,
This warning shouldn't concern. Just let's you know that somewhere in
the code free(0) was called - no side effects :-)
free(0) should never be called, so this warning _should_ concern you.
To see what's happening please try to compile with malloc debugging
on (edit Makefile.defs, remove -DF_MALLOC, add -DDBG_QM_MALLOC and
recompile everything: make proper; make all).
Use a higher debug level (warning: it will write a lot of info in the
log), and wait. Next time a free(0) will be tried ser will write
who called it in the log and then it will core dump (abort()).
Please send me the log lines above:
BUG: qm_free: bad pointer ...
(something like "qm_free(0x.., 0x..), called from ...").
Andrei