Wireshark mailing list archives
Re: core dump on starting wireshark (latest SVN update 39266?)
From: Jeff Morriss <jeff.morriss.ws () gmail com>
Date: Thu, 06 Oct 2011 09:08:36 -0400
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-request () wireshark org?subject=unsubscribe
Current thread:
- core dump on starting wireshark (latest SVN update 39266?) Kaul (Oct 05)
- Re: core dump on starting wireshark (latest SVN update 39266?) Jeff Morriss (Oct 05)
- Re: core dump on starting wireshark (latest SVN update 39266?) Bill Meier (Oct 05)
- Re: core dump on starting wireshark (latest SVN update 39266?) Kaul (Oct 05)
- Re: core dump on starting wireshark (latest SVN update 39266?) Stephen Fisher (Oct 05)
- Re: core dump on starting wireshark (latest SVN update 39266?) Kaul (Oct 06)
- Re: core dump on starting wireshark (latest SVN update 39266?) Guy Harris (Oct 06)
- Re: core dump on starting wireshark (latest SVN update 39266?) Jeff Morriss (Oct 06)
- Re: core dump on starting wireshark (latest SVN update 39266?) Kaul (Oct 05)