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

2009-08-05 Thread Guy Harris
On Aug 4, 2009, at 4:53 PM, Rich Alderson wrote: > Thanks for the debugging help. Installing the updated libraries > required for > wireshark caused Emacs to stop working, which is a major problem > since I have > been using Emacs for more than 30 years (starting with the original > MIT TE

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

2009-08-04 Thread Jaap Keuter
Hi Rich, Sorry to hear that. As far as I know (I'm a noob in Slackware) there's a decent supporting community around Slackware, maybe they can point you in the right direction. Or maybe Michiel can fill you in (see http://slackbuilds.org/repository/12.2/network/wireshark/) on the details. Hope

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

2009-08-04 Thread Rich Alderson
Thanks for the debugging help. Installing the updated libraries required for wireshark caused Emacs to stop working, which is a major problem since I have been using Emacs for more than 30 years (starting with the original MIT TECO implementation) and have no intention of changing now. I have re-

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

2009-08-02 Thread Rich Alderson
> From: Rich Alderson > Date: Sun, 2 Aug 2009 14:09:53 -0400 (EDT) >> Date: Fri, 31 Jul 2009 21:45:55 +0200 >> From: Jaap Keuter >> This top of stack seems to be the end of g_message delivery of a >> backgrounded process to TTY. Before that it's a GLIB assert on >> something pango is processin

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

2009-08-02 Thread Rich Alderson
> Date: Fri, 31 Jul 2009 21:45:55 +0200 > From: Jaap Keuter > This top of stack seems to be the end of g_message delivery of a > backgrounded process to TTY. Before that it's a GLIB assert on > something pango is processing, but it's unclear what. Maybe the > rest of the backtrace would show, but

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

2009-07-31 Thread Jaap Keuter
Hi, This top of stack seems to be the end of g_message delivery of a backgrounded process to TTY. Before that it's a GLIB assert on something pango is processing, but it's unclear what. Maybe the rest of the backtrace would show, but it's not there. Wild guess? pango / cairo libs are not up to

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

2009-07-31 Thread Rich Alderson
> From: Rich Alderson > References: <20090718012834.13fc524...@panix5.panix.com> > <20090720001958.ga6...@mobile004.mycingular.net> > Date: Mon, 20 Jul 2009 17:51:46 -0400 (EDT) >> Date: Sun, 19 Jul 2009 18:19:58 -0600 >> From: Stephen Fisher >> On Fri, Jul 17, 2009 at 09:28:34PM -0400, R

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

2009-07-20 Thread Rich Alderson
> Date: Sun, 19 Jul 2009 18:19:58 -0600 > From: Stephen Fisher > 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 la

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

2009-07-19 Thread Stephen Fisher
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. > > When I run the program, I get the following error messages: > Segmentation fault > > I'm sorry, but I'

[Wireshark-dev] Segmentation fault on startup of wireshark

2009-07-17 Thread Rich Alderson
I have just built the latest stable version of wireshark on Slackware 12.2, after building all of the prerequisites. When I run the program, I get the following error messages: MDE ~> which wireshark /usr/bin/wireshark MDE ~> ls -la /usr/bin/wireshark -rwxr-xr-x 1 root root 54089