From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from drizzle.Stanford.EDU ([36.59.0.16]) by hawkwind.utcs.utoronto.ca with SMTP id <24048>; Wed, 8 Mar 1995 12:27:00 -0500
Received: (castor@localhost) by drizzle.Stanford.EDU (8.6.8/8.6.4) id JAA18686 for sam-fans@hawkwind.utcs.toronto.edu; Wed, 8 Mar 1995 09:30:40 -0800
From:	Castor Fu <castor@drizzle.Stanford.EDU>
Message-Id: <199503081730.JAA18686@drizzle.Stanford.EDU>
Subject: sam or tk bug?
To:	sam-fans@hawkwind.utcs.toronto.edu
Date:	Wed, 8 Mar 1995 12:30:40 -0500
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I've started using sam on RS 6000's recently and have been getting
the following error relatively often (3 times in the past two days):

	Xlib:  sequence lost (0x10006 > 0xfcb) in reply type 0x0!
	X Error of failed request:  0
	  Major opcode of failed request:  0 ()
	  Serial number of failed request:  6
	  Current serial number in output stream:  4043

Then samterm exits.  Has anyone seen this before?

I think this might be connected with a Tk tool which I hacked together.
It provides some of the functionality of emacs's M-x compile, by
searching the results of a 'make' for errors, and sending in sam
commands through the named pipe.  It also has hooks for the AT&T Toolchest
'cscope' program, to provide source browsing capability.

To make it more useful, it would be nice to have easier X selection
features in 'sam'.  I think there were some chording patches a while back.
Maybe those would be most appropriate?  I guess I'll have to dig through the
archives.

	-castor