On Sun, 16 Apr 2017, Pavan Maddamsetti wrote:
> I ran a perfectly innocuous Perl one-liner in my xterm, and it printed
> the correct output. But then, the xterm stopped responding to keyboard
> input.
So, to paraphrase: "This perfectly innocuous thing broke things"?
_I_ would start by reconsidering the evaluation of the perl script as
'innocuous' and look closely at what it actually did, particurarly any
ioctls it used or escape sequences it printed that xterm might have
interpreted to put it into a weird state. Do the settings in the "control
mouse-left-button" and "control mouse-middle-button" menu match those in a
not-screwed-up xterm?
> And a sample 100 lines of ktrace output:
...
> Can anybody help me figure out what is going on. It looks like there
> are calls to select(2) and poll(2) mixed together, is this a problem?
That's part of the glory of the X client libraries. c.f.
http://www.tedunangst.com/flak/post/mplayer-ktracing
for another example of this. Not the cause of your problem.
Philip Guenther
