Monitoring event through monitor could lead to segfault

Asking to trace push_after event from monitor api lead to Segmentation fault because of an infinite loop.

Although, gerrit-review 15807 resolv this issue, I experience some random segfaults playing Low CAN scenarios tests.
I do not have pushed further my investigations at this moment but here is one stack when it happens:

{{<3> ERROR: BACKTRACE due to signal Segmentation fault/11:
[1/31] /usr/lib64/liblua-5.3.so(+0x24468) [0x7f0c694a0468]
[2/31] /usr/lib64/liblua-5.3.so(lua_next+0x20) [0x7f0c69485a60]
[3/31] /usr/lib64/liblua-5.3.so(+0x9f52) [0x7f0c69485f52]
[4/31] /usr/lib64/liblua-5.3.so(+0xa04f) [0x7f0c6948604f]
[5/31] /usr/lib64/liblua-5.3.so(luaL_traceback+0x19b) [0x7f0c69486c7b]
[6/31] /usr/lib64/liblua-5.3.so(+0x1012c) [0x7f0c6948c12c]
[7/31] /usr/lib64/liblua-5.3.so(+0x12b77) [0x7f0c6948eb77]
[8/31] /usr/lib64/liblua-5.3.so(+0x28d05) [0x7f0c694a4d05]
[9/31] /usr/lib64/liblua-5.3.so(+0x12dd8) [0x7f0c6948edd8]
[10/31] /usr/lib64/liblua-5.3.so(+0x12e05) [0x7f0c6948ee05]
[11/31] /usr/lib64/liblua-5.3.so(+0x11aae) [0x7f0c6948daae]
[12/31] /usr/lib64/liblua-5.3.so(+0x11bbd) [0x7f0c6948dbbd]
[13/31] /usr/lib64/liblua-5.3.so(+0x11c14) [0x7f0c6948dc14]
[14/31] /usr/lib64/liblua-5.3.so(+0x27dc2) [0x7f0c694a3dc2]
[15/31] /usr/lib64/liblua-5.3.so(+0x803f) [0x7f0c6948403f]
[16/31] /home/claneys/Workspace/Sources/IOTbzh/app-afb-test/build/package/lib/aft.so(+0x95e2) [0x7f0c696bf5e2]
[17/31] /home/claneys/Workspace/Sources/IOTbzh/app-afb-test/build/package/lib/aft.so(+0xaf1f) [0x7f0c696c0f1f]
[18/31] /home/claneys/Workspace/Sources/IOTbzh/app-afb-test/build/package/lib/aft.so(+0x6585) [0x7f0c696bc585]
[19/31] /home/claneys/Workspace/Sources/IOTbzh/app-afb-test/build/package/lib/aft.so(+0x9016) [0x7f0c696bf016]
[20/31] aft-low-can() [0x418b43]
[21/31] aft-low-can(afb_evt_evtid_push+0xb5) [0x43c5e6]
[22/31] aft-low-can() [0x42a252]
[23/31] aft-low-can() [0x42c1b6]
[24/31] aft-low-can() [0x42c2b7]
[25/31] aft-low-can(afb_hook_evt_push_after+0xcb) [0x421187]
[26/31] aft-low-can(afb_evt_evtid_hooked_push+0x88) [0x43c6af]
[27/31] lib/afb-low-can.so(+0x35b93) [0x7f0c6a023b93]
[28/31] lib/afb-low-can.so(+0x34024) [0x7f0c6a022024]
[29/31] /usr/lib64/libstdc++.so.6(+0xbf523) [0x7f0c69d1b523]
[30/31] /usr/lib64/libpthread.so.0(+0x7594) [0x7f0c6ea14594]
[31/31] /usr/lib64/libc.so.6(clone+0x3f) [0x7f0c6d3b90df]
[/home/claneys/Workspace/Sources/IOTbzh/appfw/app-framework-binder/src/sig-monitor.c:77,dumpstack]
}}

I continue my investigations but there are some issues to fix before being able to tell more accurately where is the glitch.