https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3661
Summary: Crash on startup when no DNS configured
Product: Wireshark
Version: 1.2.0
Platform: x86
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: webpages@xxxxxxxxxxx
Build Information:
wireshark 1.2.0 (SVN Rev 28753)
Copyright 1998-2009 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.16.2, with GLib 2.20.3, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with c-ares 1.6.0, with Lua 5.1, with GnuTLS 2.8.1, with Gcrypt 1.4.4, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Jun 15 2009), with
AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1
beta5
(packet.dll version 4.1.0.1452), based on libpcap version 1.0.0, GnuTLS 2.8.1,
Gcrypt 1.4.4, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
--
Starting wireshark goes through the normal registration of dissectors but once
at the colourful new start page a Windows error report box pops up and
wireshark quits.
Tshark behaves similarly:
tshark -i2 -p
to select the 2nd interface (which has no DNS configured) and no promiscuous
mode will happily sit waiting for packets. As soon as a packet arrives it too
crashes with Windows error report box pops up and quits.
Presumably turning off reverse lookups could work round this problem, only you
don't get an opportunity to untick it since the crash happens at the start
page.
Configuring one or more DNS servers for that interface resolves the problem.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
