Kaul wrote:
It was actually the ~/.wireshark/recent_common that caused this - and when you'll look at it, it's obvious why - though I have no clue how I got to this situation.
Is it possible the very first core you got was like mine--while writing the recent file? (Do you have all the old cores around? A quick backtrace on each would tell.)
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
