[SR-Users] Kamailio 1.5.4 crash

2010-08-30 Thread gwillingham
Kamailio 1.5.4 crashes with the following backtrace. (gdb) bt #0  free_to_params (tb=0x79ffc0) at parser/parse_to.c:79 #1  free_to (tb=0x79ffc0) at parser/parse_to.c:88 #2  0x0047fe82 in clean_hdr_field (hf=0x2b32776ec6a0) at parser/hf.c:187 #3  0x2b327492f525 in

Re: [SR-Users] Kamailio 1.5.4 crash

2010-08-30 Thread Alex Balashov
On 08/30/2010 11:33 AM, gwilling...@comcast.net wrote: output from gdb shows hf-parsed to be NULL, however the call to free_to(hf-parsed) is being called, from there bad things happen. Sounds like a double free(), or a free() of something that was never allocated. -- Alex Balashov -

Re: [SR-Users] Kamailio 1.5.4 crash

2010-08-30 Thread Henning Westerholt
On Monday 30 August 2010, Alex Balashov wrote: On 08/30/2010 11:33 AM, gwilling...@comcast.net wrote: output from gdb shows hf-parsed to be NULL, however the call to free_to(hf-parsed) is being called, from there bad things happen. Sounds like a double free(), or a free() of something that

Re: [SR-Users] Kamailio 1.5.4 crash

2010-08-30 Thread Iñaki Baz Castillo
2010/8/30 gwilling...@comcast.net: We were experiencing the issue with 1.5.4 released version, we upgraded from svn and the issue still persists.  I have a backtrace from both versions. I agree it is a free of a null pointer, but the if(hf-parsed) should be the test for NULL, and only