From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 20 18:31:50 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3900016A4DF for ; Thu, 20 Jul 2006 18:31:50 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id E498143D45 for ; Thu, 20 Jul 2006 18:31:49 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms063.mailsrvcs.net ([192.168.1.4]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0J2P008DPSSG6FA0@vms044.mailsrvcs.net> for hackers@freebsd.org; Thu, 20 Jul 2006 13:31:28 -0500 (CDT) Received: from 198.190.8.100 ([198.190.8.100]) by vms063.mailsrvcs.net (Verizon Webmail) with HTTP; Thu, 20 Jul 2006 13:31:28 -0500 (CDT) Date: Thu, 20 Jul 2006 13:31:27 -0500 (CDT) From: Sergey Babkin X-Originating-IP: [198.190.8.100] To: Peter Jeremy , babkin@users.sourceforge.net Message-id: <1887331.732121153420288819.JavaMail.root@vms063.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Thu, 20 Jul 2006 19:50:46 +0000 Cc: FreeBSD Hackers Subject: Re: Re: Re: Programs not accepting input? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 18:31:50 -0000 >From: Peter Jeremy >>BTW, I've promised Greg a script to dump the X protocol >>from binary log, then I was busy and and forgot about it. >>Is there still any interest in this tool? > >What does your script do? I've used xmon in the (distant) past but >it is designed to sit in the middle of an X connection. I think >Wireshark can decode X11. It takes a hex dump produced in whatever way (kdump, strace or maybe tcpdump) and tries to decode the X protocol fields in it. The dump can be made at either client or server side and can include both sides of transmissions (with separators between the portions of the file). Converting the output of a tracing tool into a proper raw hex dump is a separate task. I have a script that does that with output of SVR4 truss. The information about the X protocol fields gets taken from a simplistic parsing of the slightly massaged X header files. At some point I neede to trace the X protocol and I didn't know about the other tools (your e-mail is the first time I hear about them), so I've made this script. -SB