Thank's Klaus, I will re-open the bug report, I don't know what changes to fix the bug FS247...
Best Regards 2013/1/7 Klaus Darilion <klaus.mailingli...@pernau.at> > Then it seems that this fix and is not related to your bug FS247. You > should re-open the bug report. > > regards > Klaus > > > On 03.01.2013 17:21, Bruno Bresciani wrote: > >> My openSSL version is 0.9.8... According to >> http://openssl.6102.n7.nabble.**com/Custom-free-routine-is-** >> invoked-with-NULL-argument-in-**openssl-1-0-1-td25937.html<http://openssl.6102.n7.nabble.com/Custom-free-routine-is-invoked-with-NULL-argument-in-openssl-1-0-1-td25937.html> >> this was working fine in 0.9.8. >> >> I was analysing the backtrace full with gdb and the line below shows >> that ptr was not a NULL parameter. >> >> #4 0x0051a87f in ser_realloc (ptr=0xb61f0bc0, size=32) at >> ../../mem/shm_mem.h:266 >> >> ptr=0xb61f0bc0 >> size=32 >> >> Now, I'm a little confused...the changes to allow freeing of NULL >> pointer to behave like standard free () function will take effect to >> prevent the bug FS#247? >> >> Best Regards >> >> 2013/1/3 Klaus Darilion <klaus.mailingli...@pernau.at >> <mailto:klaus.mailinglists@**pernau.at <klaus.mailingli...@pernau.at>>> >> >> >> You can also check which openSSL version you are using. According to >> http://openssl.6102.n7.nabble.**__com/Custom-free-routine-is-_** >> _invoked-with-NULL-argument-**in-__openssl-1-0-1-td25937.**html >> >> <http://openssl.6102.n7.**nabble.com/Custom-free-** >> routine-is-invoked-with-NULL-**argument-in-openssl-1-0-1-**td25937.html<http://openssl.6102.n7.nabble.com/Custom-free-routine-is-invoked-with-NULL-argument-in-openssl-1-0-1-td25937.html> >> > >> it happened somewhere between 1.0.0. and 1.0.1c >> >> regards >> klaus >> >> >> On 03.01.2013 14:56, Bruno Bresciani wrote: >> >> Thank's for your reply Klaus, >> >> but I don't know if is exactly this patch that Daniel is >> referring, >> because the backtrace full with gdb showed that problem happened >> at >> ser_realloc function. I will insert this check to NULL pointer at >> ser_free and ser_realloc function and recompile kamailio 3.1.2 >> because I >> can't update to version 3.3.3 for while. >> >> Best Regards >> >> 2013/1/2 Klaus Darilion <klaus.mailingli...@pernau.at >> <mailto:klaus.mailinglists@**pernau.at<klaus.mailingli...@pernau.at> >> > >> <mailto:klaus.mailinglists@__p**ernau.at <http://pernau.at> >> >> <mailto:klaus.mailinglists@**pernau.at<klaus.mailingli...@pernau.at> >> >>> >> >> >> I think Daniel is referring to this patch: >> http://git.sip-router.org/cgi-**__bin/gitweb.cgi/sip-router/?** >> a=__commit;h=__**020acff35f8e9dfa62aba8678a781a**__0f7bbb110b<http://git.sip-router.org/cgi-__bin/gitweb.cgi/sip-router/?a=__commit;h=__020acff35f8e9dfa62aba8678a781a__0f7bbb110b> >> >> <http://git.sip-router.org/**cgi-bin/gitweb.cgi/sip-router/** >> ?a=commit;h=**020acff35f8e9dfa62aba8678a781a**0f7bbb110b<http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=020acff35f8e9dfa62aba8678a781a0f7bbb110b> >> > >> >> This fix was done to devel and 3.3 branch and is included >> in latest >> 3.3.3 release. >> >> regards >> Klaus >> >> Am 20.12.2012 19 <tel:20.12.2012%2019> >> <tel:20.12.2012%2019>:29, schrieb Bruno Bresciani: >> >> Hi, >> >> I refer the bug fix FS#247 that I open in 30 July 2012 >> and you >> closed in 25 october 2012 with the information: "Reopen >> if the >> patch for free(0) didn't work.". >> >> What Release this fix was included? >> >> >> Best Regards >> >> 2012/12/20 Daniel-Constantin Mierla <mico...@gmail.com >> <mailto:mico...@gmail.com> >> <mailto:mico...@gmail.com <mailto:mico...@gmail.com>>> >> >> >> >> Hello, >> >> 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. >> >> Cheers, >> Daniel >> >> >> On 12/20/12 6:01 PM, Bruno Bresciani wrote: >> >> Hello Daniel, >> >> 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... >> >> Best Regards >> >> 2012/8/1 Daniel-Constantin Mierla >> <mico...@gmail.com <mailto:mico...@gmail.com> >> <mailto:mico...@gmail.com >> >> <mailto:mico...@gmail.com>>> >> >> >> Hello, >> >> >> On 7/31/12 3:39 PM, Bruno Bresciani wrote: >> >> Hello, >> >> 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? >> >> >> q_malloc is more suitable for debugging. >> >> >> >> 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' >> >> >> Do you have kex module loaded? What is the >> output of >> 'kamctl fifo which'? >> >> >> >> 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. >> >> Discovering may require additional patches, >> like more >> debug messages in the C code, that's why is >> better to >> start with the latest stable. >> >> >> Cheers, >> Daniel >> >> >> Best Regards >> >> 2012/7/31 Daniel-Constantin Mierla >> <mico...@gmail.com <mailto:mico...@gmail.com> >> <mailto:mico...@gmail.com >> >> <mailto:mico...@gmail.com>>> >> >> >> Hello, >> >> >> On 7/30/12 9:01 PM, Bruno Bresciani >> wrote: >> >> Hi, >> >> 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... >> >> the log messages related to memory >> operations can be >> controlled by global parameters >> memdbg and memlog. >> >> >> >> 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? >> >> >> kamctl fifo get_statistics all >> >> and see the shared memory total >> value. It will be >> interesting to see available shared >> memory as well. >> >> >> >> 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. >> >> >> 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. >> >> Cheers, >> Daniel >> >> >> >> -- >> Daniel-Constantin Mierla - >> http://www.asipto.com >> http://twitter.com/#!/miconda >> >> <http://twitter.com/#%21/__**miconda<http://twitter.com/#%21/__miconda> >> >> <http://twitter.com/#%21/**miconda<http://twitter.com/#%21/miconda> >> >> >> >> -http://www.linkedin.com/in/__**miconda<http://www.linkedin.com/in/__miconda> >> >> >> <http://www.linkedin.com/in/**miconda<http://www.linkedin.com/in/miconda> >> > >> Kamailio Advanced Training, Seattle, USA, >> Sep 23-26, 2012 -http://asipto.com/u/katu >> >> Kamailio Practical Workshop, Netherlands, >> Sep 10-12, 2012 -http://asipto.com/u/kpw >> >> >> >> -- >> Daniel-Constantin Mierla -http://www.asipto.com >> http://twitter.com/#!/miconda >> >> <http://twitter.com/#%21/__**miconda<http://twitter.com/#%21/__miconda> >> >> <http://twitter.com/#%21/**miconda<http://twitter.com/#%21/miconda> >> >> >> >> -http://www.linkedin.com/in/__**miconda<http://www.linkedin.com/in/__miconda> >> >> <http://www.linkedin.com/in/**miconda<http://www.linkedin.com/in/miconda> >> > >> >> >> >> >> >> ______________________________**___________________ >> >> SIP Express Router (SER) and Kamailio (OpenSER) - >> sr-users mailing list >> sr-users@lists.sip-router.org >> >> <mailto:sr-us...@lists.sip-**router.org<sr-users@lists.sip-router.org> >> > >> >> <mailto:sr-us...@lists.sip-__**router.org<sr-us...@lists.sip-__router.org> >> >> <mailto:sr-us...@lists.sip-**router.org<sr-users@lists.sip-router.org> >> >> >> http://lists.sip-router.org/__** >> cgi-bin/mailman/listinfo/sr-__**users<http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users> >> <http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-** >> users <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>> >> >> >> >> ______________________________**___________________ >> >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users >> mailing list >> sr-users@lists.sip-router.org >> >> <mailto:sr-us...@lists.sip-**router.org<sr-users@lists.sip-router.org> >> > >> >> <mailto:sr-us...@lists.sip-__**router.org<sr-us...@lists.sip-__router.org> >> >> <mailto:sr-us...@lists.sip-**router.org<sr-users@lists.sip-router.org> >> >> >> >> http://lists.sip-router.org/__**cgi-bin/mailman/listinfo/sr-__** >> users <http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users>< >> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> >> > >> >> >> >> >> ______________________________**___________________ >> >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users >> mailing list >> sr-users@lists.sip-router.org <mailto:sr-us...@lists.sip-** >> router.org <sr-users@lists.sip-router.org>> >> http://lists.sip-router.org/__**cgi-bin/mailman/listinfo/sr-__** >> users <http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users>< >> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> >> > >> >> >>
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
