Wireshark · Wireshark-dev: Re: [Wireshark-dev] Segmentation fault on startup of wireshark

[Rich Alderson <wireshark@xxxxxxxxxxxxxxxxxxxxxxxx>]

> From: Rich Alderson <wireshark@xxxxxxxxxxxxxxxxxxxxxxxx>
> References: <20090718012834.13FC5242A3@xxxxxxxxxxxxxxxx>
> 	<20090720001958.GA6902@xxxxxxxxxxxxxxxxxxxxxxxx>
> Date: Mon, 20 Jul 2009 17:51:46 -0400 (EDT)

>> Date: Sun, 19 Jul 2009 18:19:58 -0600
>> From: Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx>

>> On Fri, Jul 17, 2009 at 09:28:34PM -0400, Rich Alderson wrote:

>>> I have just built the latest stable version of wireshark on Slackware 
>>> 12.2, after building all of the prerequisites.

>> Try running the GNU Debugger (gdb) and launch Wireshark from it and show 
>> us the back trace so we can get an idea of what is going on.  It's 
>> pretty simple:

>> >gdb wireshark
>>  <snip>
>> (gdb) run
>>  <receive segmentation fault message>
>> (gdb) bt 10

 [ snip ]

> Please note the transcribed octal in stack frame #3.  The 8-bit characters
> kept driving emacs nuts when I c&p'd from the window in which I was running
> wireshark, so I had to paste them into an emacs on that window and
> transcribe.  It's <capital O-acute>\205<capital U-umlaut><mu>iy<capital
> U-umlaut><mu>Es<capital O-circumflex><mu>\024 on my screen, in case that's
> actually important to know.

I posted the requested gdb traceback a week and a half ago.  Does no one have
anything to say about it?  I'll remind you that I am not a C programmer, and
need a lot of help interpreting the results so that I can get on with the
actual work that this is holding up.

                                                                Rich Alderson