@henningw this is wrong no?
it should be
```
pkg_free(bmt->start);
shm_free(bmt);
```
instead.
you can't access ``bmt->start`` if you freed ``bmt`` first, no?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/d7770cae2ee68be7184298b2bb41cb0…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/d7770cae2ee68be7184298b2bb41cb0ba3ebb47d/105547932(a)github.com>
In the above case, `SHM_MEM_ERROR` is losing the usefulness of the previous version of the log message, there is `SHM_MEM_ERROR_FMT` that should be used.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/0702a7e0d9df2867cbc86188c06d953…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/0702a7e0d9df2867cbc86188c06d95363d484d5a/105546658(a)github.com>
Probably the `parse_error` label should be replaced by `error` and all `goto`'s point to it. `parse_error` is used for other cases like target pv not being writeable, it's difference comparing with `error` is printing more context info about the position in the string where the error happens.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/01e82b38c41d344c1e94b2e0f574981…
You are receiving this because you commented.
Message ID: <kamailio/kamailio/commit/01e82b38c41d344c1e94b2e0f574981ef0ce4318/105547846(a)github.com>
Is it intended to jump to `error` instead of `parse_error` now? @pantelisk98 @henningw
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/01e82b38c41d344c1e94b2e0f574981…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/01e82b38c41d344c1e94b2e0f574981ef0ce4318/105530322(a)github.com>