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 11813] New: Basic Dissector guide still refers to create_d

Date: Sun, 29 Nov 2015 22:24:53 +0000
Bug ID 11813
Summary Basic Dissector guide still refers to create_dissector_handle
Product Web sites
Version N/A
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Main site - www.wireshark.org
Assignee [email protected]
Reporter [email protected]

Build Information:
Version 2.1.0-TmSyncro (v2.1.0rc0-844-g6952c1c from master)

Copyright 1998-2015 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 Qt 5.5.1, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, with
AirPcap 4.1.0 build 1622.
Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (with SSE4.2), with 8082MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 31101
--
The Wireshark Developer's Guide for Wireshark 2.1 in Chapter 9.2 provides
guidance regarding creating a basic C dissector.

Example 9.2 shows the use of create_dissector_handle.  This function is
deprecated to new_create_dissector_handle, and in fact is no longer available
in the build detailed above.

Similarly, Example 9.4 shows a dissector function with a void return.  This is
no longer valid as the dissector should return an int value reflecting the
bytes consumed.

There are other related errors in Example 9.8, 9.11 and possibly 9.20.

Best regards...Paul


You are receiving this mail because:
  • You are watching all bug changes.