... It is a matter of utility, not of havoc.
Ok. this was a just suggestion. That it has caused such negative reaction, I've seen before in other venues, and I'm sorry.For my part, I know what I can do to handle my concerns when or if I decide to improve the error reporting and debugging situation on Emacs. Yes, I am sorry I didn't say at the outset that this is were I envision this getting used.Yes, an easy to follow use case would be helpful.
I am very much in favor of improving Emacs' error messages, especially anything that leads to the source of an error when a backtrace is not produced.
If you can explain how something you envision could make that happen, then you'll likely see feedback change.
BTW, I think there might be a good idea in there about using hash codes to verify valid use of a file,
though my personal experience is that incompatible byte codes are well reported by Emacs and have not caused me any problems to date.
The much bigger problem is tracing an error raised from C code back to the source function that raised it when running without a C debugger active. Without that, users can't provide much of a bug report except possibly how to trigger the problem.
Bob