Wireshark-dev: Re: [Wireshark-dev] Wireshark bug on startup
Jeff Morriss wrote on Thu, 07 Jan 2010
11:55:02 -0500
>Paul Bjork wrote:
>> When I try to run Wireshark
1.2.5 with WinCap 4.1.1 (?, the latest as
>> of today) I get just
to the startup initializing screen. It says
>>
>> "Initializing dissectors"
>>
>> then it hangs and is not salvageable
even using end task in the task
>> manager.
>>
>> I'm running Windows 2000 SP4
on an instance of a virtual machine using
>> the latest copy of VirtualBox
(3.1.2) from Sun, on a Mac mini with an
>> intel core 2 duo processor.
>>
>> Any ideas?
>
>Sounds a lot like:
>
>https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3270
I have Wireshark 1.2.5 and WinPcap 4.1.1
working with no problem on a real Win2k system:
Microsoft Windows 2000, 5.00.2195, Service
Pack 4
x86 Family 6 Model 8 Stepping 3, AT/AT
COMPATIBLE, 130,544 KB RAM
As it happens I never tried Wireshark
1.0.x on that old machine, and having read bug 3270 I'd rather not try
it. I've used various 1.2.x and 1.3.x versions with no problem. (Using
the work-around from bug 4176 after 1.3.1-SVN-30666.) Based on libgcrypt
versions I should have seen bug 3270 for all before 1.3.3-SVN-xxxxx. So
do 1.2.x and 1.3.x do something different with libgcrypt to avoid the bug?
