I am using the -g option and already tried to trap the error with a debugger, but the erroneous variable "e3" is never used or set (except the declaration) till the line at which the exception is thrown. I have absolutely no clue what's causing the exception.