-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
include extra context in compiler and linker errors #218
Comments
Reversing is already good enough to do this. For example, for #315:
Edit: looks like just the field names aren't reversed, but still, the rest is helpful. |
Fields names are reversed as of 0150aa8 right? |
Also, is there any reason we wouldn't want to automatically reverse the error message(s) instead of making the user reverse the error messages themselves? |
Yep, I fixed that shortly after posting the comment.
That's what this issue is about :) My last comment just says that |
Dropping this from the milestone because it doesn't seem urgent. |
For example, from a recent bug report:
If I was debugging this failure manually, I'd have to do a bunch of debugging to figure out what original bit of code the obfuscated names like
ZU31i
actually refer to.This is unnecessary, and the errors are unnecessarily hostile to the average user. We should, at least, provide context as to what was the original name of each of these.
We could probably reuse the work from #5 here. We would print the usual build error, and then print its un-garbled version too if any garbled identifiers were found.
The text was updated successfully, but these errors were encountered: