I got it.
I will update it just as it had done in $sht(...).
On Mon, Feb 25, 2019 at 2:45 PM Daniel-Constantin Mierla <
notifications@github.com> wrote:
> It doesn't seem safe what you do there, because you copy the value of the
> item in a new variable, then unlock the slot. But the value can be a string
> and that will point in share memory. By unlocking, the item in hash table
> can be deleted or modified, making the previous string value invalid.
>
> See how is the function for pv get of $sht(...), there is a deep cloning
> of the item.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/kamailio/kamailio/pull/1866#issuecomment-466973400>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ArE2rFNa0SskW3IB0Pc8LulNFOoGAfHrks5vQ8XfgaJpZM4bPk66>
> .
>
--
--Mojtaba Esfandiari.S
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.