On 10/3/12 8:35 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
You can go and update in f_malloc and backport, if it is a solution that
is ok for you.
i committed the LOG -> MDBG change to master. i still don't understand
though, why it is only me who is seeing those warnings, sin
Daniel-Constantin Mierla writes:
> You can go and update in f_malloc and backport, if it is a solution that
> is ok for you.
i committed the LOG -> MDBG change to master. i still don't understand
though, why it is only me who is seeing those warnings, since it is
highly unlikely that others don
This is actually the reason I moved the check for free(0) before the
check of the memory address range. Someone reported on irc that libssl
does free(0) causing core dump due to an internal abort() executed in
qm_free(p), if p is less than minimum memory address (which was the case
when p=0).
Daniel-Constantin Mierla writes:
> Anyhow, I pushed a patch to master branch to print the file and line for
> free(0) when compiled with memdbg=1.
>
> Try it to see if you get the details of free(0) location.
daniel,
thanks for the patch. i now got bunch of these at shutdown:
Oct 2 22:43:54
Strange, unless it is related to mem debug logs.
Anyhow, I pushed a patch to master branch to print the file and line for
free(0) when compiled with memdbg=1.
Try it to see if you get the details of free(0) location.
Cheers,
Daniel
On 10/2/12 9:18 PM, Juha Heinanen wrote:
Daniel-Constantin
Daniel-Constantin Mierla writes:
> But now do you get the messages related to alloc and free operations?
yes.
>
> It should be first the message from mem/q_malloc.c, line 437, after it
> is the condition on free(0).
i see lots of these kind of entries, but no free(0) entries:
Oct 2 21:56:02
Quite strange I would say.
No, debug parameter value does not replace warning level with debug -
just to comment on your previous message related to it.
But now do you get the messages related to alloc and free operations?
It should be first the message from mem/q_malloc.c, line 437, after it
Daniel-Constantin Mierla writes:
> You have to set memdbg (or memlog) parameters to lower value than
> debug.
now i have
memdbg=1
memlog=1
debug=2
and when i stop sip-proxy i still don't get any free(0) warnings. i do
get the warnings if i have not set memdbg and memlog.
-- juha
You have to set memdbg (or memlog) parameters to lower value than debug.
Cheers,
Daniel
On 2 Oct 2012, at 16:57, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> Better change the Makefile.defs and set MEMDBG=1 inside it.
>
> ok, i added this to my debian/rules:
>
># Turn on
Daniel-Constantin Mierla writes:
> Better change the Makefile.defs and set MEMDBG=1 inside it.
ok, i added this to my debian/rules:
# Turn on memory debuging
sed -i -e 's/MEMDBG ?= 0/MEMDBG ?= 1/' Makefile.defs
after build, i checked in source dir that the change took effect:
/
I think debian has its own rules file for generating the make command.
Better change the Makefile.defs and set MEMDBG=1 inside it.
Cheers,
Daniel
On 10/2/12 3:31 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
It is what MEMDBG=1 does, adds some compile flags and removes others.
i
Daniel-Constantin Mierla writes:
> It is what MEMDBG=1 does, adds some compile flags and removes others.
is there something i would need to remove?
> Have you tried make proper?
i made each time debian package from scratch, i.e., my script copies
source tree from git to an empty directory and t
On 10/2/12 3:06 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
I just tried 'make cfg MEMDBG=1' and the -DDBG_QM_MALLOC is there (you
can check config.mak).
i added directly to -DDBG_QM_MALLOC to CFLAGS:
/usr/bin/make cfg CC=cc CFLAGS="-Wall -DDBG_QM_MALLOC -g" MEMDBG=1 QUIET=1
Daniel-Constantin Mierla writes:
> I just tried 'make cfg MEMDBG=1' and the -DDBG_QM_MALLOC is there (you
> can check config.mak).
i added directly to -DDBG_QM_MALLOC to CFLAGS:
/usr/bin/make cfg CC=cc CFLAGS="-Wall -DDBG_QM_MALLOC -g" MEMDBG=1 QUIET=1
FMSTATS=1 KMSTATS=1 MAIN_NAME=sip-proxy
I just tried 'make cfg MEMDBG=1' and the -DDBG_QM_MALLOC is there (you
can check config.mak).
Do a make proper before.
Cheers,
Daniel
On 10/2/12 2:25 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Interesting, after compiling in the source tree, can you paste the
output of:
./ka
Daniel-Constantin Mierla writes:
> Interesting, after compiling in the source tree, can you paste the
> output of:
>
> ./kamailio -I
>
> (that's an upper case i).
given in source dir after compilation:
/usr/src/trunk-src/openxg-sip-proxy$ ./sip-proxy -I
Print out of sip-proxy internals
Vers
On 10/2/12 1:53 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
What version are you using? Being fm_free, means it is without mem debug
on, so it should be same behavior as before. This memory manager does
not keep track of locations for malloc/free, you have to recompile with
MEMDB
Daniel-Constantin Mierla writes:
> What version are you using? Being fm_free, means it is without mem debug
> on, so it should be same behavior as before. This memory manager does
> not keep track of locations for malloc/free, you have to recompile with
> MEMDBG=1 and then you should see the lo
Daniel-Constantin Mierla writes:
> What version are you using? Being fm_free, means it is without mem debug
> on, so it should be same behavior as before. This memory manager does
> not keep track of locations for malloc/free, you have to recompile with
> MEMDBG=1 and then you should see the lo
Hello,
I moved the check for *free(0) before the check for range (min and max
address of pkg/shm) - 0 is out of range always and the range check was
done only for mem debugging mode.
What version are you using? Being fm_free, means it is without mem debug
on, so it should be same behavior as
at some point i have started to get these kind of warning when i stop my
sip proxy:
--text follows this line--
Oct 1 10:23:01 siika /usr/sbin/sip-proxy[16970]: WARNING:
[mem/f_malloc.c:512]: WARNING:fm_free: free(0) called
any idea where they come from or how i could found out where they come
f
21 matches
Mail list logo
