Comment # 3
on bug 10395
from Kevin Cox
(In reply to Evan Huus from comment #2)
>
> I've already uploaded a fix for the main issue (the memory accesses) but
> there's also the assertion: Actual length does not equal expected.
>
Yeah, this shouldn't happen.
> Does this simply indicate a malformed packet? If that is so, it should be
> replaced by an expert info. If it actually indicates a bug in your code,
> could you please take a look at fixing it?
>
No, it means that the length-extraction function and the actual dissection
functions are out of sync, I will look into it.
You are receiving this mail because:
- You are watching all bug changes.