Comment # 14
on bug 7359
from Chris Maynard
Well it was definitely a preference setting. I believe it has to do with the
snmp_users file format differences between 1.8 and latest trunk (probably 1.10
too). Either that, or somehow - not sure how - the snmp_users file was
modified to be:
# This file is automatically generated, DO NOT MODIFY.
,"pippo","MD5","PIPPO","DES",""
,"pippo2","SHA1","PIPPO2","DES",""
,"pippo3","SHA1","PIPPO3","AES",""
,"pippo4","MD5","PIPPO4","AES",""
instead of:
# This file is automatically generated, DO NOT MODIFY.
,"pippo","MD5","pippoxxx","DES","PIPPOxxx"
,"pippo2","SHA1","pippoxxx","DES","PIPPOxxx"
,"pippo3","SHA1","pippoxxx","AES","PIPPOxxx"
,"pippo4","MD5","pippoxxx","AES","PIPPOxxx"
Switching between using 1.8 and latest trunk definitely has other problems too,
as I've noticed that columns changes seem to always revert to the defaults when
saving preferences between the 2 versions.
So I guess the problem that led to this one is trying to run different versions
of Wireshark on the same machine. Ideally, Wireshark-1.8 would use
1.8-specific preferences, Wireshark-1.10 would use 1.10-specific preferences,
etc.
I suppose either way though, Wireshark shouldn't be dividing by zero regardless
of the contents of the snmp_users file ... should it?