| Bug ID |
8093
|
| Summary |
frame_proto_data freed between frames
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
TShark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
--
In tshark.c when doing a first pass through the capture file the
frame_proto_data is freed between every frame.
line 3214 of tshark.c:
if (do_dissection) {
epan_dissect_cleanup(&edt);
frame_data_cleanup(&fdata);
}
Why is frame_data_cleanup() called here? Either this behaivour is correct -
frame protocol data should be freed - in which case 'frame_data_cleanup' does
not free the memory, or frame_data_cleanup should not be called in the first
place. Wireshark does not do this.
This causes a problem for my dissector, which looks at the prior frame's proto
data. Under tshark this data is gone.
You are receiving this mail because:
- You are watching all bug changes.
