Wireshark-bugs: [Wireshark-bugs] [Bug 8519] decode nfs4 fslocation error when location's count i
Comment # 3
on bug 8519
from fanchaoting
(In reply to comment #2)
> When using your pcap file with 1.9.2-48543 or 1.8.7-48420, I go not have any
> error displaying frame 9981 and the NFS location dissection is:
> recc_attr: FATTR4_FS_LOCATIONS (24)
> fattr4_fs_locations
> pathname components (0)
> fs_location4:
> no values
>
> I suspect that you are using 1.6 branch as the dissect_rpc_array code in 1.8
> branch and later was changed so as to replace
> if( num == 0 ){
> proto_tree_add_none_format(tree, hfindex, tvb, offset, 4,
> "no values");
> offset += 4;
>
> return offset;
> }
> by
> if(num == 0) {
> proto_tree_add_text(lock_tree, tvb, offset, 4, "no values");
> offset += 4;
>
> proto_item_set_end(lock_item, tvb, offset);
>
> return offset;
> }
> This change is related to bug 8145. I added it to the backport list for
> 1.6.15.
> In the meantime, I suggest you to either apply the change locally or upgrade
> to Wireshark 1.8.6.
>
> *** This bug has been marked as a duplicate of bug 8145 ***
thanks i'll upgrade to Wireshark 1.8.6 and test it.
You are receiving this mail because:
- You are watching all bug changes.
