Comment # 24
on bug 9952
from Peter Wu
(In reply to Jeff Morriss from comment #11)
> The problem only shows up with Valgrind so the only way to find the
> offending packet was to split the capture into pieces until I got down to 1
> frame. I attached that one frame.
When using `valgrind --db-attach=yes`, you have the ability to start a debugger
when a problem is detected. Very useful if you use valgrind in such cases!
Currently compiling with autotools and cmake to compare for other possible
missing dissectors.
You are receiving this mail because:
- You are watching all bug changes.
