Hello,
just for the record, some guidelines about enabling memory debugging are
posted on the dokuwiki:
http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory#how_to_handle_it
Cheers,
Daniel
On 09/13/07 09:58, Bogdan-Andrei Iancu wrote:
Hi Juha,
Looks like the module domain.so has the extra flag "DBG_F_MALLOC". Be
sure the module is cleaned and recompiled and in the local makefile
there are no extra defines.
BTW, while setting DBG_QM_MALLOC, be sure you disable *all* the other
"*_MALLOC" flags.
Regards,
Bogdan
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
> Yes, nothing shows up as by default memory logs are printed using
DBG > level. So, either set mem_log=L_ERR to have the mem logs on
ERR level, > either set debug=6 to get all debugs (including mem logs)
i know that but the problem is that after i compiled openser with memory
debugging on, it refused to start because of this:
> > Sep 12 18:16:14 tutpro openser: core:version_control: module
compile flags mismatch for /usr/lib/openser/modules/domain.so core:
STATS: Off, USE_TCP, USE_TLS, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_QM_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT module: STATS: Off, USE_TCP, USE_TLS,
DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC,
DBG_QM_MALLOC, DBG_F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
may be i'm trying to do too many things at the same time.
-- juha
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
