Wireshark-dev: Re: [Wireshark-dev] wireshark 0.99.7 crash on MacOS X 10.5 (Leopard)
From: Andreas Fink <[email protected]>
Date: Thu, 3 Jan 2008 20:59:01 +0100
On 03.01.2008, at 20:44, Guy Harris wrote:

Andreas Fink wrote:

I'm trying to rebuild wireshark for MacOS X 10.5 (Leopard) with the new
X11 engine (instead of the old XFree86, Leopard uses XFree.org's
implementation if I'm not mistaken).
X.org rather than XFree.org, but, yes, Leopard's X server is X.org- 
based
rather than XFree86-based.
ok I screwed up the names in my posting but basically what you say is  
what I see.


However I'm running into crashes
saying:

intelix:sources afink$ wireshark --sync
The program 'wireshark' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
 (Details: serial 57553 error_code 8 request_code 152 minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
  that is, you will receive the error a while after causing it.
  To debug your program, run it with the --sync command line
  option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
X server bug.  See

	http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1953

for details and, at the end, for information on where to get a fixed X
server.

(Summary, for X geeks: the server temporarily set the depth of a
drawable for some purpose and, in some error cases, failed to restore it
to the correct value when done.)
ok. So I can safely blame Leopard of bringing me a broken X11.app... ;-)
by the way I think it happens when it starts scrolling lines.
I also noted that it happens also with Monitor set to thousands of colors instead of millions in my case. I'm running it on a 23" external monitor while having the internal monitor of the laptop as secondary screen. And yes I set both monitors to thousands of colors at testing (usually its set on millions on both).