Wireshark-bugs: [Wireshark-bugs] [Bug 9303] some DCERPC fragment are not identify leading to cor
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 05 Nov 2013 14:39:42 +0000

Comment # 14 on bug 9303 from 
(In reply to comment #12)
> What about changing it to a Gslist with the protocol handles or proto id
> prepended that is always built? The string could be constructed from the
> list of handles/ids when needed and possibly saved.

That's definitely a possibility - I don't know if it would be faster than
building the string directly though. I'm honestly a bit surprised how
significant to performance that ended up being, so I'm wondering if there's
some other path it's triggering that isn't obvious... 

(In reply to comment #13)
> The GSlist should be in frame data.

Why? We'd have to clear it whenever preferences changed anyways, and we have no
use for it between dissections.

You are receiving this mail because:
  • You are watching all bug changes.