First time here? Check out the FAQ!

Ask Your Question
0

How can I see where Lua dissector gets aborted?

asked Mar 12 '4

Armali gravatar image

updated Mar 13 '4

I have a Lua plugin dissector which in some cases (for some packet in a file when it's opened, but not when clicked on the packet) 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. No error dialog box, no red packet details line and no Lua console message shows up when the error in the registered dissector code occurs. Isn't there any way to get informed about the place and cause of dissector script abortion?

Preview: (hide)

1 Answer

Sort by » oldest newest most voted
0

answered Mar 13 '4

Armali gravatar image

I think there must be a better way, but the only one I've found (besides inserting prints here and there) is setting a debug line hook like

function hookl(event, line)
    print(event..' '..line..' '..tostring(debug.getinfo(2).name))
end

    debug.sethook(hookl, 'l')

    debug.sethook()

and seeing where the console output stops.

Preview: (hide)
link

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: Mar 12 '4

Seen: 167 times

Last updated: Mar 13 '24