Premature death of all top-levels under Windows

[Jocelyn Paine <popx at pop3 dot ifs dot org dot uk>]

I sent a message a few days ago about a problem with the Windows
top-level: the way some error messages don't appear until several prompts
after the error that caused them. I've found another funny:

Every time that I run the top-level (with java kawa.repl -w), it
eventually seizes up and stops responding to input. In fact, it won't even
echo what I type. The following error trace appears in the DOS window from
which I started it:

  Exception occurred during event dispatching:
  java.lang.StringIndexOutOfBoundsException: String index out of range: 29395
        at java.lang.String.substring(Compiled Code)
        at kawa.MessageArea.enter(Compiled Code)
        at kawa.MessageArea.keyPressed(Compiled Code)
        at java.awt.Component.processKeyEvent(Compiled Code)
        at java.awt.Component.processEvent(Compiled Code)
        at java.awt.TextComponent.processEvent(Compiled Code)
        at java.awt.Component.dispatchEventImpl(Compiled Code)
        at java.awt.Component.dispatchEvent(Compiled Code)
        at java.awt.EventQueue.dispatchEvent(Compiled Code)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:68)

Quite a nuisance this is, because it means I lose my carefully
set-up variables and have to reset them in another session. It looks as
though some buffer area representing the interactive window is
overflowing.

Jocelyn Paine
http://www.ifs.org.uk/~popx/
+44 (0)7768 534 091