Wireshark-bugs: [Wireshark-bugs] [Bug 5575] Patch to fix memory leaks/errors in Lua plugin
Date: Fri, 14 Jan 2011 12:29:31 -0800 (PST)

Robert G. Jakabosky <[email protected]> changed:

           What    |Removed                     |Added
           Priority|Low                         |Medium

--- Comment #4 from Robert G. Jakabosky <[email protected]> 2011-01-14 12:29:30 PST ---
(In reply to comment #0)
> the Lua call-stack is not being unwound when a WireShark exception is thrown
> during the executation of a Lua dissector.

Here is a bit more details about this problem.  The Lua state has a max C-call
limit of 200 (i.e. call stack: C -> Lua -> C -> Lua -> C.....).  When a
WireShark exception is thrown the current C-call depth (and stack state) are
not clean-up and after about 200 malformed packets WireShark can no-longer make
calls into the Lua state, it just keeps getting an error "C stack overflow"
thrown from Lua and you have to restart WireShark before Lua works again.

Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.