How to improve workflow for creating a Lua-based Wireshark dissector
Posted
by
piyo
on Stack Overflow
See other posts from Stack Overflow
or by piyo
Published on 2010-08-31T23:08:31Z
Indexed on
2011/01/01
17:54 UTC
Read the original article
Hit count: 247
I've finally created a Dissector for my UDP protocol in Lua for Wireshark, but the work flow is just horrendous. It consists of editing my custom Lua file in my editor, then double-clicking my example capture file to launch Wireshark to see the changes. If there was an error, Wireshark informs me via dialogs or a red line in the Tree analysis sub-pane. I then re-edit my custom Lua file and then close that Wireshark instance, then double-click my example capture file again. It's like compiling a C file and only seeing one compiler error at a time.
Is there a better (faster) way of looking at my changes, without having to restart Wireshark all the time?
At the time, I was using Wireshark 1.2.9 for Windows with Lua enabled.
© Stack Overflow or respective owner