Path: utzoo!attcan!uunet!ginosko!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!jim
From: jim@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: xterm mouse button bindings problem
Message-ID: <8910181256.AA10228@kanga.lcs.mit.edu>
Date: 18 Oct 89 12:56:29 GMT
References: <8910181220.AA03245@LYRE.MIT.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 11


	2) If I first hit button three, (with the mouse cursor in the window
	   for several seconds) invariably, the xterm is terminated.

    I'll bet you have a large saveLines resource
    and that xterm is therefore trying to store a very large CUT_BUFFER0
    property.  Xterm is buggy in that it doesn't intelligently handle
    resource allocation failures of this nature...

I'd say it sounds more like Peter is running stock R3 without public
patch #4 (available via ftp from expo or the xstuff mail server)....