I have a Lua plugin dissector which in some cases apparently doesn't run to its end (observed through Lua console printout at entry and exit); it seems silently aborted at some point, I guess due to some error within. I can produce such behavior by inserting an error (e. g. call of an undefined function) in the code - though an error dialog box appears if the error is in the initialization code executed when loading the plugin, no dialog, no red packet details line and no Lua console message shows up when the error in the actual registered dissector code is hit. Isn't there any way to get informed about the place and cause of dissector script abortion?