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 7313] Correct ERF name, add WTAP_ENCAP string display

Date: Thu, 31 May 2012 22:04:54 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7313

--- Comment #4 from Stephen Donnelly <stephen@xxxxxxxxxx> 2012-05-31 22:04:53 PDT ---
(In reply to comment #3)
> I'm fine with patch (I didn't know that we link libwireshark with libwiretap).

ldd on libwireshark suggests that it is?

$ ldd /usr/local/lib/libwireshark.so.0
..
    libwiretap.so.0 => /usr/local/lib/libwiretap.so.0 (0x00007fbb00d8c000)
..

> But wouldn't be better to build value_string array for all encaps, and use it
> in hf_frame_wtap_encap?

The 'hf_register_info' will only work with a static value_string array,
correct? I'm not sure how/if they can be used with dissector tables. When would
you build the value_string?

As noted I'm not sure this is the best way to do this, although it appears to
work.

It would be nice to be able to map the frame.interface_id to the
wtap.interface_data[i]->if_name or if_description string as well, but I can't
see how to get there from here.

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