Hi all.
I see this message in my syslog
Nov 17 10:50:00 sip01 /usr/local/sbin/ser[30968]: WARNING:fm_free: free(0) called
Is this a something that I should be concerned with?
Regards, Paul
__________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com
Hi Paul,
This warning shouldn't concern. Just let's you know that somewhere in the code free(0) was called - no side effects :-)
Best regards, Marian
Java Rockx wrote:
Hi all.
I see this message in my syslog
Nov 17 10:50:00 sip01 /usr/local/sbin/ser[30968]: WARNING:fm_free: free(0) called
Is this a something that I should be concerned with?
Regards, Paul
__________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
On Nov 17, 2004 at 18:24, Marian Dumitru marian.dumitru@voice-sistem.ro wrote:
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
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@voice-sistem.ro wrote:
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
Andrei,
I'm not sure how this problem disappeared, but I did upgrade from -dev12 to -dev16
I no longer see the warnings.
Regards, Paul
--- Andrei Pelinescu-Onciul pelinescu-onciul@fokus.fraunhofer.de wrote:
On Nov 17, 2004 at 18:24, Marian Dumitru marian.dumitru@voice-sistem.ro wrote:
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
__________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com
-
Andrei Pelinescu-Onciul -
Java Rockx -
Marian Dumitru