https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3961
--- Comment #15 from Guy Harris <guy@xxxxxxxxxxxx> 2010-12-05 18:04:44 PST ---
If you've created a capture file of *any* sort that causes a Wireshark crash
(for reasons other than "it ran out of memory because the capture was too
big"), file a bug on that; Wireshark *does* support the general notion of a
capture file with multiple link-layer types (that dates back to before pcap-ng
support was added), and the pcap-ng reader uses that capability, so if there's
a multiple-link-layer-type file that causes a crash in Wireshark, that's a bug
that we should fix (and, if possible, put the fix into the 1.4 *and* 1.2
branches - the pcap-ng support, complete with code to use WTAP_ENCAP_PER_PACKET
and keep track of multiple interfaces, dates back to 1.2.0).
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.