Newsgroups: comp.windows.x
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!dont-send-mail-to-path-lines
From: tomt@maui.coral.COM (Tom Tulinsky)
Subject: Debugging an X server
Message-ID: <9105151920.AA00893@maui.coral.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
References: <VICTOR.91May14174033@irt.watson.ibm.com>
Date: 15 May 91 19:20:51 GMT
Lines: 32


)
) 
) What are recommended ways to debug an X server?  There is a client
) (info explorer on AIX 3.1 on the RS/6000) which always causes my X
) server (an IBM rt/pc running BSD 4.3) to crash with a core dump.   The
) same client also causes X servers on RS/6000's running Mach 2.5 to
) freeze up.  To my way of thinking this is certainly a bug on the part
) of the servers, but it would be neccessary to find out what sort of
) trash this client is sending.
) --

To find out what is being sent to the server use 'xscope' (from the
contrib/clients dir).  It dumps out all traffic between X and the
client.  The documentation is a little confusing; to do everything on
one workstation, called 'myws', do:
    xscope -i1 -v2 > file        (create virtual display myws:1)
in another window:
    anyxclient -display myws:1.0 

It's quite possible that the bug will be fixed in the next patch of
X; that was what I found when this happened to me.


 Coral
     * **	Tom Tulinsky                508 460-6010
  *  **		Coral Network Corporation   fax 508 481-6258
*  ** 		734 Forest St               net: tomt@coral.com
 ***		   Marlboro, MA 01752		
  **		   U S A
*********	   Overheard in a BART station:
NETWORKS	      "I was the only NORM there!"