Yes, the weird stuff at the end is Robospeak for the location where the error occured. Upside: Double click on the message and it jumps right to the error :)
I had to encode the exact location in there in order to make it more stable (before it was regexing the location from the String XXX - Line X, column y, but that didn't work all too well with external files.
Also, with Tools -> Enable call stack, you'll get a nice call stack so you can trace back the error.