I reproduced on my machine the condition you described. I executed 13!:11 '' (last error number) ater the session returned to immediate execution:
populate 100 Current 1 Failed 0 Current 2 Failed 0 Current 3 Failed 0 ... Current 36 Failed 0 Current 37 Failed 0 13!:11 '' 55 The 55 indicates "throw", which on the face of it could be legitimate. (An uncaught throw returns the session to immediate execution.) Since the netflix.ijs script does not contain "throw." I assume the throw is generated somewhere in the bowels of jdb? ----- Original Message ----- From: Oleg Kobchenko <[EMAIL PROTECTED]> Date: Wednesday, October 22, 2008 0:31 Subject: [Jgeneral] Verb abruptly ends without error To: General forum <[email protected]> > Testing a case of JDB > > http://www.jsoftware.com/jwiki/OlegKobchenko/JDB_Netflix > > there came a strange situation when a verb abruptly > exited without error. The example is easily reproducible > using the small script on Wiki. > > It looks like a case of stress-testing on J memory system. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
