| Bug ID | 
          10815
           | 
        
        
          | Summary | 
          Lua: getting fieldinfo.value for FT_NONE causes assert
           | 
        
        
          | Product | 
          Wireshark
           | 
        
        
          | Version | 
          1.99.x (Experimental)
           | 
        
        
          | Hardware | 
          x86
           | 
        
        
          | OS | 
          Mac OS X 10.4
           | 
        
        
          | Status | 
          UNCONFIRMED
           | 
        
        
          | Severity | 
          Normal
           | 
        
        
          | Priority | 
          Low
           | 
        
        
          | Component | 
          Dissection engine (libwireshark)
           | 
        
        
          | Assignee | 
          [email protected]
           | 
        
        
          | Reporter | 
          [email protected]
           | 
        
      
        
        Build Information:
Wireshark 1.99.2
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with GTK+ 2.24.17, with Cairo 1.12.14, with Pango 1.30.1,
with
libpcap, without POSIX capabilities, with libz 1.2.8, with GLib 2.36.0, with
SMI
0.4.8, with c-ares 1.10.0, with Lua 5.2, with GnuTLS 3.1.22, with Gcrypt 1.5.3,
with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Jul 11 2014
17:33:32), with AirPcap.
Running on Mac OS X 10.9.5, build 13F34 (Darwin 13.4.0), with locale
en_US.UTF-8, with libpcap version 1.6.2, with libz 1.2.8, with GnuTLS 2.12.19,
with Gcrypt 1.5.0, without AirPcap.
Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz (with SSE4.2)
Built using clang 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56).
--
Retrieving an FT_NONE field's value through `fieldinfo.value` or `fieldinfo()`
causes an assert.  The current C-code for FieldInfo__call() falls through to
calling fvalue_get(), which isn't valid for an FT_NONE.
         
      
      
      You are receiving this mail because:
      
      
          - You are watching all bug changes.