Wireshark · Wireshark-dev: Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)

Wireshark-dev: Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)

From: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>

Date: Thu, 06 Oct 2011 09:08:36 -0400

Kaul wrote:

It was actually the ~/.wireshark/recent_common that caused this - andwhen you'll look at it, it's obvious why - though I have no clue how Igot to this situation.

Is it possible the very first core you got was like mine--while writingthe recent file? (Do you have all the old cores around? A quickbacktrace on each would tell.)

References:
- [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
  - From: Kaul
- Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
  - From: Bill Meier
- Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
  - From: Kaul
- Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
  - From: Stephen Fisher
- Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
  - From: Kaul

Prev by Date: Re: [Wireshark-dev] Couldn't load module / undefined symbol:
Next by Date: Re: [Wireshark-dev] Couldn't load module / undefined symbol:
Previous by thread: Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
Next by thread: [Wireshark-dev] Can g_warning() be removed from gtk/main_menubar.c
Index(es):
- Date
- Thread