[OpenSIPS-Devel] [OpenSIPS/opensips] 78740c: evi: More verbose about which param caused crash

[Peter Lemenkov]

  Branch: refs/heads/3.1
  Home:   https://github.com/OpenSIPS/opensips
  Commit: 78740cf44e8a6db3f1e4771f16dba8fad8fdbdb3
      https://github.com/OpenSIPS/opensips/commit/78740cf44e8a6db3f1e4771f16dba8fad8fdbdb3
  Author: Peter Lemenkov <lemenkov at gmail.com>
  Date:   2020-09-02 (Wed, 02 Sep 2020)

  Changed paths:
    M evi/evi_transport.c
    M modules/event_datagram/event_datagram.c
    M modules/event_rabbitmq/event_rabbitmq.c
    M modules/event_stream/stream_send.c

  Log Message:
  -----------
  evi: More verbose about which param caused crash

When using evi interface sometimes we need to know exactly which
parameter led to failure. At least we need its name and event's name.

Signed-off-by: Peter Lemenkov <lemenkov at gmail.com>
(cherry picked from commit 9ee8c06484dc8fa50a8c9ab44a6a9e7e7aa40e21)


  Commit: 72592f679dff3b0ad046df8e5e4ab0a5560b1ed4
      https://github.com/OpenSIPS/opensips/commit/72592f679dff3b0ad046df8e5e4ab0a5560b1ed4
  Author: Peter Lemenkov <lemenkov at gmail.com>
  Date:   2020-09-02 (Wed, 02 Sep 2020)

  Changed paths:
    M evi/evi_transport.c

  Log Message:
  -----------
  evi: Str params can contain NULL values.

NULL value as a str param is totally fine according to JSON
specification. So let's not crash when adding str parameter with NULL
value.

Signed-off-by: Peter Lemenkov <lemenkov at gmail.com>
(cherry picked from commit b801f04c4acc970e4c37bae736d0c0518ab0958b)


Compare: https://github.com/OpenSIPS/opensips/compare/9cf948b22fab...72592f679dff