This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

tshark -H name resolution broken in 1.12.1 ?

0

Can anybody confirm that with 1.12.1 the host name resolution doesn't work anymore?

hosts file:

# Name Resolution with wireshark / tshark  
10.55.56.168 net1.host1
10.49.50.61  net2.host2

Command

Z:\traces>tshark -r trace.ee.cap -H hosts -w trace.ee.pcapng -v -W n
(tshark.exe:3900): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
(tshark.exe:3900): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed
(tshark.exe:3900): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
(tshark.exe:3900): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed
TShark 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)
Copyright 1998-2014 Gerald Combs <[email protected]> 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 (64-bit) with GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with
SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, without Python, with GnuTLS 3.1.22,
with Gcrypt 1.6.0, without Kerberos, with GeoIP.
Running on 64-bit Windows 7 Service Pack 1, build 7601, without WinPcap.
Intel Xeon E312xx (Sandy Bridge), with 3558MB of physical memory.
Built using Microsoft Visual C++ 10.0 build 40219

Edit:

I submitted Bug 10507 for this problem

asked 26 Sep '14, 07:23

mrEEde's gravatar image

mrEEde
3.9k152270
accept rate: 20%

edited 26 Sep '14, 12:58


One Answer:

0

Hi, the assertions should be removed but are harmless. In your command line I can see that you give -v option. Did you mean -V instead?

EDIT: I confirm the issue (resolution results are not stored in pcapng file). Could you please fill a bug to http://bugs.wireshark.org?

answered 26 Sep '14, 09:35

Pascal%20Quantin's gravatar image

Pascal Quantin
5.5k1060
accept rate: 30%

edited 26 Sep '14, 11:13

Thanks, Bug 10507 Submitted

(26 Sep '14, 12:59) mrEEde

Fixed in 1.12.1

(16 Oct '14, 22:52) mrEEde