<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
if you refer to free(0) issue with libssl, I am not sure it was ever
put in 3.1 branch, as the last release was before reporting the
issue.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 12/20/12 6:01 PM, Bruno Bresciani
wrote:<br>
</div>
<blockquote
cite="mid:CAKv6Mrb4c2JNbbXeWE3rXL=Xx7-ncZPHiq8Nc2q4fRO4iz3yRA@mail.gmail.com"
type="cite">Hello Daniel,<br>
<br>
What patch this bug was fixed? This bug was open in 30 July 2012
and ultimate Release to 3.1.X (3.1.6) was released at 14 July
2012...<br>
<br>
Best Regards<br>
<br>
<div class="gmail_quote">2012/8/1 Daniel-Constantin Mierla <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hello,
<div class="im"><br>
<br>
<div>On 7/31/12 3:39 PM, Bruno Bresciani wrote:<br>
</div>
<blockquote type="cite">Hello,<br>
<br>
I didn't know that log messages related to memory
operations can be controlled by global parameter, but I
like to know if is recommendable I recompile kamailio
using q_malloc (default) and not f_malloc... memory
operations using q_malloc is more reliable and avoid
problems or crashes or it is only more suitable for
debugging? What do you suggest Daniel?<br>
</blockquote>
<br>
</div>
q_malloc is more suitable for debugging.
<div class="im"><br>
<br>
<blockquote type="cite"> <br>
The 'get_statistics all' command is avaliable by a
specific module? I run 'kamctl fifo get_statistics all'
and return '500 command 'get_statistics' not available'<br>
</blockquote>
<br>
</div>
Do you have kex module loaded? What is the output of 'kamctl
fifo which'?
<div class="im"><br>
<br>
<blockquote type="cite"><br>
For while is impossible to start a new installation,
first because I don't know how much time I will spend to
port and second because I am involved with other
developments and I have no time to make this. I know
that 3.1 is no longer a official branch but now start a
new installation it's very very difficult, my in
intention is discover what caused the crash and if
exists a way to fix or prevent it.<br>
</blockquote>
</div>
Discovering may require additional patches, like more debug
messages in the C code, that's why is better to start with
the latest stable.
<div class="im"><br>
<br>
Cheers,<br>
Daniel<br>
<br>
<blockquote type="cite"> <br>
Best Regards<br>
<br>
<div class="gmail_quote">2012/7/31 Daniel-Constantin
Mierla <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hello,
<div><br>
<br>
<div>On 7/30/12 9:01 PM, Bruno Bresciani wrote:<br>
</div>
</div>
<blockquote type="cite">Hi, <br>
<br>
<div> I compiled kamailio with MEMDBG = 0
because I didn't want the memory debug in
kamailio log, but I didn't know these turns on
f_malloc and disabling q_malloc...<br>
</div>
</blockquote>
the log messages related to memory operations can
be controlled by global parameters memdbg and
memlog.
<div><br>
<br>
<blockquote type="cite"><br>
Probably the size of shared memory that I
start kamailio is 32MB because I didn't gave a
different -m parameter value, exist a command
to verify this information?<br>
</blockquote>
<br>
</div>
kamctl fifo get_statistics all<br>
<br>
and see the shared memory total value. It will be
interesting to see available shared memory as
well.
<div><br>
<br>
<blockquote type="cite"> <br>
At moment that crash happened, there were few
registered users agents and were being made
tests with register and calls with TLS
protocol. I got only the two situations that I
showed at first email.<br>
</blockquote>
<br>
</div>
If you plan to start a new installation, I
strongly recommend 3.3 branch, the code is more
actual and easier to debug. 3.1 is no longer an
official maintained branch, those being now 3.3
and 3.2. I'm looking at this issue to be sure it
is no longer in latest stable.<br>
<br>
Cheers,<br>
Daniel
<div>
<div><br>
<br>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
<div class="im">
<pre cols="72">--
Daniel-Constantin Mierla - <a moz-do-not-send="true" href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a moz-do-not-send="true" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a moz-do-not-send="true" href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - <a moz-do-not-send="true" href="http://asipto.com/u/katu" target="_blank">http://asipto.com/u/katu</a>
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - <a moz-do-not-send="true" href="http://asipto.com/u/kpw" target="_blank">http://asipto.com/u/kpw</a></pre>
</div>
</div>
</blockquote>
</div>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a></pre>
</body>
</html>