http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2492
Summary: 1.0.0 crash when parsing MIBs, but 0.99.6 don't
Product: Wireshark
Version: 1.1.0
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Major
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: leon728@xxxxxxxxx
Build Information:
wireshark 1.0.0
Copyright 1998-2008 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.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.5,
with ADNS, with Lua 5.1, with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
--
Config WireShark to load the same MIBs.
In 0.99.6, it works well.
In 1.0.0, it crashed on startup.
I am sure it's caused by loading MIBs.
If I remove SMI settings, it starts normally.
I have to point out, my MIBs can only pass paring level 'Lenient' on my MIB
browser (AdventNet's MIB Browser).
I tried to modified MIBs to pass level 'Normal'.
Sometimes it solves the problem. But most of the time, it doesn't.
So I don't think MIBs are not the problem.
I also tried to change the loading order of SMI modules.
Sometimes it solves the problem, though I don't think it's the right solution.
I think the root cause of this problem is, what's the difference of MIB parse
between 0.99.6 and 1.0.0 ?
I am not providing my MIBs at this time, because it's owned by my company
In case you need MIBs to test this bug, please inform me and I'll try to give a
copy (with some modification).
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.