You have to install debugging symbols to have any useful lead. On the other hand, problems
are startup can appear any time, trying to catch everything wrong there could bring a lot
of complexity.
For an interpreter that focuses to be fast at runtime and offer a quick restart, trying to
cover all the errors at startup that can crash (instead of a smoother shut down) may bring
costs in performance that can impact the restart with good configs. So these two benefits
have to be balanced:
* smooth shutdown on starting with broken config
* quick start with valid config
We still have to see what is the cause of the crash here, just saying it needs proper
consideration of benefits vs drawbacks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2599#issuecomment-756343453