Comment # 8
on bug 9463
from Bill Meier
The one thing I've found so far:
At some point, the struct epan_session pointed to by cfile.epan is freed (via
epan_free) but cfile.colinfo.epan still has the address of the now freed
*cfile.epan and thus later a crash occurs when colinfo.epan->get_frame_ts is
referenced.
This pretty much matches the info in Comment #5.
ISTR that there's tricky stuff going on with respect to all of this; something
about there's effectively multiple threads of execution due to the dissection
going on when data is fetched for display ? (and with separate distinct
instances of certain data structures ?).
You are receiving this mail because:
- You are watching all bug changes.