Re: [sr-dev] Multiple memleaks and segfauts in Kamailio v5.0.4

2017-12-04 Thread M S
Super. I will test it and report back. Many thanks and kind regards. On Mon, Dec 4, 2017 at 9:48 AM, Daniel-Constantin Mierla wrote: > I think I catch this one, too -- I pushed a patch for it to branch 5.0 as > well. > > Cheers, > Daniel > > On 04.12.17 03:49, M S wrote: > > For "pv_buffer_slo

Re: [sr-dev] Multiple memleaks and segfauts in Kamailio v5.0.4

2017-12-04 Thread Daniel-Constantin Mierla
I think I catch this one, too -- I pushed a patch for it to branch 5.0 as well. Cheers, Daniel On 04.12.17 03:49, M S wrote: > For "pv_buffer_slots" issue, kamailio crashes during startup and there > is no core dump. What should i do about it? > > Here is what i see in logs (just one log line).

Re: [sr-dev] Multiple memleaks and segfauts in Kamailio v5.0.4

2017-12-03 Thread M S
For "pv_buffer_slots" issue, kamailio crashes during startup and there is no core dump. What should i do about it? Here is what i see in logs (just one log line). -- Dec 4 03:44:19 webrtc-as-rct kernel: [1814300.507165] kamailio[16879] segfault at c0c0c0c7 ip b7700239 sp bfd9a0f8 error 7 in libc

Re: [sr-dev] Multiple memleaks and segfauts in Kamailio v5.0.4

2017-12-03 Thread M S
Thanks @Daniel, i am opening up the tickets. @Juha, we are not dumping sip trace to db but rather to a udp socket (typically 127.0.0.1:5060), where we can observer them using ngrep or sipgrep cli utilities. The whole purpose is to watch sip trace at runtime while conducting our tests and observe t

[sr-dev] Multiple memleaks and segfauts in Kamailio v5.0.4

2017-12-03 Thread Juha Heinanen
M S writes: > 1. Calling sip_trace method without any arguements or with only one > arguement (duplicate uri) crashes kamailio with segfault. My K does not crash when I make call like this: setflag(TRACE); sip_trace(); but I have not defined as many vars as you, but only these: # -- si

Re: [sr-dev] Multiple memleaks and segfauts in Kamailio v5.0.4

2017-12-03 Thread Daniel-Constantin Mierla
Hello, if you get a crash, then take the backtrace from the corefile with gdb (inside the gdb session inspecting the corefile, do "bt full"), it is very useful information to discover where the crash happens. It is also better to open on issue on bug tracker, so the investigation of the crash can

[sr-dev] Multiple memleaks and segfauts in Kamailio v5.0.4

2017-12-03 Thread M S
Hi, I have kamailio v5.0.4 git rev. 5f26a4e8c55cdf5a5a7eaf6864c4f5213d321293 installed on 32bit Debian Wheezy virtual machine (1GB RAM and 1 vCPU) for development and testing of a project. We need to inspect sip traces to / from webrtc endpoint on kamailio side, for which we use siptrace module w