[OpenSIPS-Users] async- issues- 2.2.2
Ramachandran, Agalya (Contractor)
Agalya_Ramachandran at comcast.com
Thu Jan 19 10:00:07 EST 2017
Got it. Thank you.
From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Razvan Crainea
Sent: Thursday, January 19, 2017 3:30 AM
To: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] async- issues- 2.2.2
You have my answer inline.
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com<http://www.opensips-solutions.com>
On 01/18/2017 08:17 PM, Ramachandran, Agalya (Contractor) wrote:
Hi Razvan,
Got your point. I tried to increase the MAX_CONTENT_TYPE_LEN and tested async call and it is working fine without crash.
But one more question.
The same piece of code am using for sync REST_API query too in rest_put() method. There also print_buff is only being used.
It is working absolutely fine in the case of sync call even if the MAX_CONTENT_TYPE_LEN – is 64.
Wondering what would be the reason in sync call, it is working and in async it is not?
Pure luck. You are doing a buffer overflow, overwriting the data section. Probably when doing sync calls, nobody is using the data you are overwriting. But if it doesn't crash it doesn't mean it is ok :).
Regards,
Agalya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170119/96429d15/attachment.html>
More information about the Users
mailing list