Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

Great, thanks! On Thu, 13 Jun 2019, 11:47 Daniel-Constantin Mierla Ok, good it was sorted out. > > Cheers, > Daniel > > On 12.06.19 12:51, Mojtaba wrote: > > I solved it,too. > > All issue was from didn't allocate pkg memory. > > Thank you. > > > > On Wed, Jun 12, 2019 at 11:04 AM Daniel-Constant

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

Ok, good it was sorted out. Cheers, Daniel On 12.06.19 12:51, Mojtaba wrote: > I solved it,too. > All issue was from didn't allocate pkg memory. > Thank you. > > On Wed, Jun 12, 2019 at 11:04 AM Daniel-Constantin Mierla > wrote: >> What crash with htable api? I can't see anything related in this

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

I solved it,too. All issue was from didn't allocate pkg memory. Thank you. On Wed, Jun 12, 2019 at 11:04 AM Daniel-Constantin Mierla wrote: > > What crash with htable api? I can't see anything related in this discussion. > > On 11.06.19 17:15, Mojtaba wrote: > > Thank you. > And what about the cr

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

What crash with htable api? I can't see anything related in this discussion. On 11.06.19 17:15, Mojtaba wrote: > Thank you. > And what about the crash when using it with htable api module? > > On Tue, 11 Jun 2019, 18:18 Daniel-Constantin Mierla wrote: > > Yes, you m

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

Thank you. And what about the crash when using it with htable api module? On Tue, 11 Jun 2019, 18:18 Daniel-Constantin Mierla Yes, you must allocate with pkg, because at the end those chunks are > freed, once the new message is built. You can also look at how other > operations with data lumps ar

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

Yes, you must allocate with pkg, because at the end those chunks are freed, once the new message is built. You can also look at how other operations with data lumps are done inside the textops module. On 11.06.19 14:44, Mojtaba wrote: > I assigned a const sdp string to it just for checking. Does i

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

I assigned a const sdp string to it just for checking. Does it matter to allocate new memory for newbody? On Tue, 11 Jun 2019, 15:22 Daniel-Constantin Mierla Hello, > > how do you set newbody.s and newbody.len? > > Daniel > > On 11.06.19 12:29, Mojtaba wrote: > > Not yet, because it is under deve

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

Hello, how do you set newbody.s and newbody.len? Daniel On 11.06.19 12:29, Mojtaba wrote: > Not yet, because it is under developing, i could paste it here right away. > > { > . > . > . > body.s = get_body(msg); > if (body.s == 0) { > LM_ERR("failed to get the message b

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

Not yet, because it is under developing, i could paste it here right away. { . . . body.s = get_body(msg); if (body.s == 0) { LM_ERR("failed to get the message body\n"); return -1; } body.len = msg->len - (int) (body.s - msg->buf); //body.len = strlen

Re: [SR-Users] CRITICAL ERROR in data_lamp.c!

Hello, likely you didn't allocate the pointer inserted in data lump list. Is the code using data lumps available to look at on git? Cheers, Daniel On 11.06.19 12:01, Mojtaba wrote: > Hello, > What does this CRITICAL error mean? > Jun 11 05:48:13 debian8 /usr/local/sbin/kamailio[8468]: {1 1 INVIT

[SR-Users] CRITICAL ERROR in data_lamp.c!

Hello, What does this CRITICAL error mean? Jun 11 05:48:13 debian8 /usr/local/sbin/kamailio[8468]: {1 1 INVITE Njg0MzNhMzJhOTY3MzQ3NmNlNWY0ODkzMTJmNTM1ZTk.} CRITICAL: [core/mem/q_malloc.c:486]: qm_free(): BUG: bad pointer 0xa3c188 (out of memory block!) called from core: core/data_lump.c: free_lum