On Jan 8, 2009, at 10:32 PM, Pascal Quantin wrote:
you are right and this was fixed in trunk by revision 24759 ( http://anonsvn.wireshark.org/viewvc?view=rev&revision=24759 ).
It also appears to be fixed in Wireshark 1.0.5 (and possibly some earlier 10.0.x releases); 1.0.0 isn't the current 1.0.x release.