Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 3513] Lua dissector field registration broken

Date: Fri, 17 Sep 2010 08:24:00 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3513

Guan Hao <hguan@xxxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hguan@xxxxxxxxxxxxxx
           Platform|Other                       |x86
            Version|1.1.x (Experimental)        |1.4.0
         OS/Version|Mac OS X 10.5               |Ubuntu

--- Comment #5 from Guan Hao <hguan@xxxxxxxxxxxxxx> 2010-09-17 08:23:55 PDT ---
I can still reproduce this bug now. Here is my build information:

  wireshark 1.4.0

  Copyright 1998-2010 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.21.7, (32-bit) with GLib 2.25.15, with libpcap 1.1.1,
with
  libz 1.2.3.4, without POSIX capabilities, without libpcre, without SMI,
without
  c-ares, without ADNS, with Lua 5.1, without Python, without GnuTLS, without
  Gcrypt, with MIT Kerberos, without GeoIP, without PortAudio, without AirPcap.

  Running on Linux 2.6.35-19-generic, with libpcap version 1.1.1, with libz
  1.2.3.4.

  Built using gcc 4.4.5.
----------
I am using Ubuntu Linux 10.10 beta, however I believe this affects all
platform.

I got exactly the same result as Andrew: I wrote a dissector in lua with some
ProtoFields defined. It works well and the fields can be used in a filter
expression, however if I create a tap which use a Field extractor to extract
data of the fields, it just cannot find them.

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