Rob Fitzpatrick
ProgressTalk.com Sponsor
Just to play devil's advocate: not every error is associated with a particular line of code. Lock table overflow would be an example as it happens on the server, not in a particular client.However for a start, I seriously think I'd save dozens of wasted hours per year if they could just added file name/line number to error messages (everywhere, not just in the UI and AppServer logs).
But I totally agree that "Write to NFS file system failed on fd 109" or "Write to NFS file system failed on fd 109" would be a lot more helpful after the fact if I knew which file it was. Is it possible the runtime doesn't *know* the file name at the time the error is thrown, and just uses a file descriptor to access it? I don't know.