Thank's Klaus,<br><br>I will re-open the bug report, I don't know what changes to fix the bug FS247...<br><br>Best Regards<br><br><div class="gmail_quote">2013/1/7 Klaus Darilion <span dir="ltr"><<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@pernau.at</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Then it seems that this fix and is not related to your bug FS247. You should re-open the bug report.<br>
<br>
regards<br>
Klaus<div class="im"><br>
<br>
On 03.01.2013 17:21, Bruno Bresciani wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
My openSSL version is 0.9.8... According to<br>
<a href="http://openssl.6102.n7.nabble.com/Custom-free-routine-is-invoked-with-NULL-argument-in-openssl-1-0-1-td25937.html" target="_blank">http://openssl.6102.n7.nabble.<u></u>com/Custom-free-routine-is-<u></u>invoked-with-NULL-argument-in-<u></u>openssl-1-0-1-td25937.html</a><br>
this was working fine in 0.9.8.<br>
<br>
I was analysing the backtrace full with gdb and the line below shows<br>
that ptr was not a NULL parameter.<br>
<br>
#4 0x0051a87f in ser_realloc (ptr=0xb61f0bc0, size=32) at<br>
../../mem/shm_mem.h:266<br>
<br>
ptr=0xb61f0bc0<br>
size=32<br>
<br>
Now, I'm a little confused...the changes to allow freeing of NULL<br>
pointer to behave like standard free () function will take effect to<br>
prevent the bug FS#247?<br>
<br>
Best Regards<br>
<br>
2013/1/3 Klaus Darilion <<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@pernau.at</a><br></div>
<mailto:<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@<u></u>pernau.at</a>>><div class="im"><br>
<br>
You can also check which openSSL version you are using. According to<br></div>
<a href="http://openssl.6102.n7.nabble." target="_blank">http://openssl.6102.n7.nabble.</a><u></u>__com/Custom-free-routine-is-_<u></u>_invoked-with-NULL-argument-<u></u>in-__openssl-1-0-1-td25937.<u></u>html<div class="im">
<br>
<<a href="http://openssl.6102.n7.nabble.com/Custom-free-routine-is-invoked-with-NULL-argument-in-openssl-1-0-1-td25937.html" target="_blank">http://openssl.6102.n7.<u></u>nabble.com/Custom-free-<u></u>routine-is-invoked-with-NULL-<u></u>argument-in-openssl-1-0-1-<u></u>td25937.html</a>><br>
it happened somewhere between 1.0.0. and 1.0.1c<br>
<br>
regards<br>
klaus<br>
<br>
<br>
On 03.01.2013 14:56, Bruno Bresciani wrote:<br>
<br>
Thank's for your reply Klaus,<br>
<br>
but I don't know if is exactly this patch that Daniel is referring,<br>
because the backtrace full with gdb showed that problem happened at<br>
ser_realloc function. I will insert this check to NULL pointer at<br>
ser_free and ser_realloc function and recompile kamailio 3.1.2<br>
because I<br>
can't update to version 3.3.3 for while.<br>
<br>
Best Regards<br>
<br>
2013/1/2 Klaus Darilion <<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@pernau.at</a><br>
<mailto:<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@<u></u>pernau.at</a>><br></div>
<mailto:<a href="mailto:klaus.mailinglists@" target="_blank">klaus.mailinglists@</a>__<a href="http://pernau.at" target="_blank">p<u></u>ernau.at</a><div class="im"><br>
<mailto:<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@<u></u>pernau.at</a>>>><br>
<br>
<br>
I think Daniel is referring to this patch:<br></div>
<a href="http://git.sip-router.org/cgi-__bin/gitweb.cgi/sip-router/?a=__commit;h=__020acff35f8e9dfa62aba8678a781a__0f7bbb110b" target="_blank">http://git.sip-router.org/cgi-<u></u>__bin/gitweb.cgi/sip-router/?<u></u>a=__commit;h=__<u></u>020acff35f8e9dfa62aba8678a781a<u></u>__0f7bbb110b</a><div class="im">
<br>
<<a href="http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=020acff35f8e9dfa62aba8678a781a0f7bbb110b" target="_blank">http://git.sip-router.org/<u></u>cgi-bin/gitweb.cgi/sip-router/<u></u>?a=commit;h=<u></u>020acff35f8e9dfa62aba8678a781a<u></u>0f7bbb110b</a>><br>
<br>
This fix was done to devel and 3.3 branch and is included<br>
in latest<br>
3.3.3 release.<br>
<br>
regards<br>
Klaus<br>
<br>
Am <a href="tel:20.12.2012%2019" value="+12012201219" target="_blank">20.12.2012 19</a> <tel:20.12.2012%2019><br>
<tel:20.12.2012%2019>:29, schrieb Bruno Bresciani:<br>
<br>
Hi,<br>
<br>
I refer the bug fix FS#247 that I open in 30 July 2012<br>
and you<br>
closed in 25 october 2012 with the information: "Reopen<br>
if the<br>
patch for free(0) didn't work.".<br>
<br>
What Release this fix was included?<br>
<br>
<br>
Best Regards<br>
<br>
2012/12/20 Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a><br>
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>><br></div>
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>>><div class="im"><br>
<br>
<br>
Hello,<br>
<br>
if you refer to free(0) issue with libssl, I am not<br>
sure it<br>
was ever put in 3.1 branch, as the last release was<br>
before<br>
reporting the issue.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<br>
On 12/20/12 6:01 PM, Bruno Bresciani wrote:<br>
<br>
Hello Daniel,<br>
<br>
What patch this bug was fixed? This bug was<br>
open in 30 July<br>
2012 and ultimate Release to 3.1.X (3.1.6) was<br>
released at<br>
14 July 2012...<br>
<br>
Best Regards<br>
<br>
2012/8/1 Daniel-Constantin Mierla<br>
<<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>><br></div>
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a><div><div class="h5"><br>
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>>><br>
<br>
<br>
Hello,<br>
<br>
<br>
On 7/31/12 3:39 PM, Bruno Bresciani wrote:<br>
<br>
Hello,<br>
<br>
I didn't know that log messages related<br>
to memory<br>
operations can be controlled by global<br>
parameter, but I<br>
like to know if is recommendable I<br>
recompile kamailio<br>
using q_malloc (default) and not<br>
f_malloc... memory<br>
operations using q_malloc is more<br>
reliable and avoid<br>
problems or crashes or it is only more<br>
suitable for<br>
debugging? What do you suggest Daniel?<br>
<br>
<br>
q_malloc is more suitable for debugging.<br>
<br>
<br>
<br>
The 'get_statistics all' command is<br>
avaliable by a<br>
specific module? I run 'kamctl fifo<br>
get_statistics all'<br>
and return '500 command<br>
'get_statistics' not available'<br>
<br>
<br>
Do you have kex module loaded? What is the<br>
output of<br>
'kamctl fifo which'?<br>
<br>
<br>
<br>
For while is impossible to start a new<br>
installation,<br>
first because I don't know how much<br>
time I will spend to<br>
port and second because I am involved<br>
with other<br>
developments and I have no time to<br>
make this. I know<br>
that 3.1 is no longer a official branch<br>
but now start a<br>
new installation it's very very<br>
difficult, my in<br>
intention is discover what caused the<br>
crash and if<br>
exists a way to fix or prevent it.<br>
<br>
Discovering may require additional patches,<br>
like more<br>
debug messages in the C code, that's why is<br>
better to<br>
start with the latest stable.<br>
<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<br>
Best Regards<br>
<br>
2012/7/31 Daniel-Constantin Mierla<br>
<<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a> <mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>><br></div></div>
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a><div><div class="h5"><br>
<mailto:<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>>><br>
<br>
<br>
Hello,<br>
<br>
<br>
On 7/30/12 9:01 PM, Bruno Bresciani<br>
wrote:<br>
<br>
Hi,<br>
<br>
I compiled kamailio with MEMDBG<br>
= 0 because I<br>
didn't want the memory debug<br>
in kamailio log, but<br>
I didn't know these turns on<br>
f_malloc and disabling<br>
q_malloc...<br>
<br>
the log messages related to memory<br>
operations can be<br>
controlled by global parameters<br>
memdbg and memlog.<br>
<br>
<br>
<br>
Probably the size of shared<br>
memory that I start<br>
kamailio is 32MB because I<br>
didn't gave a different<br>
-m parameter value, exist a<br>
command to verify this<br>
information?<br>
<br>
<br>
kamctl fifo get_statistics all<br>
<br>
and see the shared memory total<br>
value. It will be<br>
interesting to see available shared<br>
memory as well.<br>
<br>
<br>
<br>
At moment that crash happened,<br>
there were few<br>
registered users agents and<br>
were being made tests<br>
with register and calls with<br>
TLS protocol. I got<br>
only the two situations that I<br>
showed at first email.<br>
<br>
<br>
If you plan to start a new<br>
installation, I strongly<br>
recommend 3.3 branch, the code is<br>
more actual and<br>
easier to debug. 3.1 is no longer<br>
an official<br>
maintained branch, those being now<br>
3.3 and 3.2. I'm<br>
looking at this issue to be sure it<br>
is no longer in<br>
latest stable.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<br>
<br>
--<br>
Daniel-Constantin Mierla -<a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a><br>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a><br></div></div>
<<a href="http://twitter.com/#%21/__miconda" target="_blank">http://twitter.com/#%21/__<u></u>miconda</a><br>
<<a href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#%21/<u></u>miconda</a>>><br>
-<a href="http://www.linkedin.com/in/__miconda" target="_blank">http://www.linkedin.com/in/__<u></u>miconda</a><div class="im"><br>
<<a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/<u></u>miconda</a>><br>
Kamailio Advanced Training, Seattle, USA,<br>
Sep 23-26, 2012 -<a href="http://asipto.com/u/katu" target="_blank">http://asipto.com/u/katu</a><br>
<br>
Kamailio Practical Workshop, Netherlands,<br>
Sep 10-12, 2012 -<a href="http://asipto.com/u/kpw" target="_blank">http://asipto.com/u/kpw</a><br>
<br>
<br>
<br>
--<br>
Daniel-Constantin Mierla -<a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a><br>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a><br></div>
<<a href="http://twitter.com/#%21/__miconda" target="_blank">http://twitter.com/#%21/__<u></u>miconda</a><br>
<<a href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#%21/<u></u>miconda</a>>><br>
-<a href="http://www.linkedin.com/in/__miconda" target="_blank">http://www.linkedin.com/in/__<u></u>miconda</a><br>
<<a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/<u></u>miconda</a>><br>
<br>
<br>
<br>
<br>
<br>
______________________________<u></u>___________________<div class="im"><br>
SIP Express Router (SER) and Kamailio (OpenSER) -<br>
sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<mailto:<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-<u></u>router.org</a>><br></div>
<mailto:<a href="mailto:sr-users@lists.sip-__router.org" target="_blank">sr-users@lists.sip-__<u></u>router.org</a><br>
<mailto:<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-<u></u>router.org</a>>><br>
<a href="http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users" target="_blank">http://lists.sip-router.org/__<u></u>cgi-bin/mailman/listinfo/sr-__<u></u>users</a><br>
<<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>users</a>><br>
<br>
<br>
<br>
______________________________<u></u>___________________<div class="im"><br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users<br>
mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<mailto:<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-<u></u>router.org</a>><br></div>
<mailto:<a href="mailto:sr-users@lists.sip-__router.org" target="_blank">sr-users@lists.sip-__<u></u>router.org</a><br>
<mailto:<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-<u></u>router.org</a>>><br>
<br>
<a href="http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users" target="_blank">http://lists.sip-router.org/__<u></u>cgi-bin/mailman/listinfo/sr-__<u></u>users</a> <<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>users</a>><br>
<br>
<br>
<br>
<br>
______________________________<u></u>___________________<div class="im"><br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users<br>
mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a> <mailto:<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-<u></u>router.org</a>><br>
</div>
<a href="http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users" target="_blank">http://lists.sip-router.org/__<u></u>cgi-bin/mailman/listinfo/sr-__<u></u>users</a> <<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>users</a>><br>
<br>
<br>
</blockquote>
</blockquote></div><br>