On Thu, Jan 06, 2000 at 03:16:18PM -0500, Phil Gregory wrote:
> (I'm not deliberately looking for these things. Really.)
>
> Found another small bug. I'd started a program i was working on and,
> though the screen didn't change, the "X II" that indicates that keyboard
> input is inhibited appeared. I hit ^R and then enter to run the program
> again. tn5250 crashed with "Assertion 0 failed at session.c, line 336."
I'm not sure how to handle this case. The 'Read' command is finished, so
we don't know how to transmit to the host again if we need to. I'm not
sure the host would appreciate it, either.
System Request should work fine. I've changed the state of the
keyboard between reads from X II to X SYSTEM, although X SYSTEM will allow
you to reset it as well. The difference, though, is that keystrokes entered
while the keyboard is X SYSTEM will get queued for the next screen. This is
what I thought we were doing before, but I may have broke it :(
I think in this case, the only legal way out would be System Request,
and we should enforce that. My next update should handle this a little
better and I'll put it on my TODO list to solve for good.
>
> Upon closer inspection, my program had been running, just not displaying
> any output (stuck in infinite recursion). I'm not sure how important this
> fact is. Someone certainly wasn't expecting something.
>
> As usual, tracefile is attached.
-Jay 'Eraserhead' Felice
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to [EMAIL PROTECTED]
| To subscribe to this list send email to [EMAIL PROTECTED]
| To unsubscribe from this list send email to [EMAIL PROTECTED]
| Questions should be directed to the list owner/operator: [EMAIL PROTECTED]
+---
