Strangest Java NZEC

[bulda_e_bien_]

Hello everyone,

I was attempting to solve problem YODANESS in Java. Not a specially difficult problem, but my solution is giving NZEC. I thought this was suspicious, so I wrapped my entire main code within a general try-catch block.

try { /* main program */ } catch (Throwable trh) { }

If it was really giving a runtime error, then the new outcome would have to be a Wrong Answer. Never the less, it is giving NZEC still. Do you guys have some idea of what may be happening? Could it be a bug in the judge?

Thanks in advance!

P.D: I have static declarations, but no static code. All inicializations were done within main, so I could wrap everything in the try-catch block.

[system]

There is some bug in the judge, instead of Time Limit Exceeded its showing NZEC.

[bulda_e_bien_]

Thanks vipul! I thought that could be the case, so I reimplemented my solution in C++ and got accepted. TLE must have been because of Java's slow input processing (using Scanner). Maybe SPOJ administrators should take a look at this. A RE message can be quite misleading if it was really a TLE, hehe.