https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3510
Summary: Lua tap functions not called
Product: Wireshark
Version: 1.1.x (Experimental)
Platform: All
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: abaxter@xxxxxxxxxxxxxxxxx
Created an attachment (id=3085)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3085)
The simple tap code I used to test lua tap functionality
Build Information:
wireshark 1.1.3
Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 2.16.1, with GLib 2.20.1, with libpcap 0.9.5, with libz
1.2.3, without POSIX capabilities, without libpcre, without SMI, without
c-ares,
without ADNS, with Lua 5.1, without GnuTLS, without Gcrypt, with MIT Kerberos,
without GeoIP, without PortAudio, without AirPcap.
NOTE: this build doesn't support the "matches" operator for Wireshark filter
syntax.
Running on Darwin 9.7.0 (MacOS 10.5.7), with libpcap version 0.9.5.
Built using gcc 4.0.1 (Apple Inc. build 5490).
--
After creating a tap with "Listener.new()", supplying packet, draw, and reset
functions, and loading a packet capture, none of the functions are called.
I used the tap example from
http://www.wireshark.org/docs/wsug_html_chunked/wslua_tap_example.html and
added print statements at the top, at the top of "menuable_tap" and in each of
"tap.packet", "tap.draw" and "tap.reset". Only the first two print statements
were called - none of the tap callbacks are ever called.
I have gotten a Lua dissector working flawlessly with this build.
I keep on getting the feeling I missed some crucial piece of Lua documentation,
but despite all my googling skills, such information seems entirely
nonexistent.
This also occurred in 1.0.7.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
