Replies: 1 comment
-
Great idea: We've talked about this a bunch of times. You identify some of the issues. We've looked at (and are still considering using) something like backtrace.io to do this (we generously have a license). The issues are, like you say:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
An idea that I just had, in context of GCC, but should likewise apply to any kind of compiler. If a user's code triggers an Internal Compiler Error (ICE), that's -- by definition -- always a bug in the compiler, and the respective compiler's upstream developers should be interested in hearing about this, to fix their implementation. Could CE help by offering an easy way to submit the "offending" code, compilation flags, etc. upstream? (If the respective upstream does like getting such reports.)
CE would need to have logic to detect an ICE (in particular to differentiate it from a normal failed compilation due to invalid source code, compilation flags, etc. (GCC: abnormal exit status, and internal compiler error string in output, I suppose.)
CE would need to know where/how to report a bug upstream. (Bugzilla, GitHub, etc.)
GCC has a command-line flag
-freport-bug
to Collect and dump debug information into a temporary file if an internal compiler error (ICE) occurs, which should be handy.GCC examples:
I have not yet considered how this relates to users' data privacy.
I have not yet considered the danger of DoS against upstream bug tracker.
If there's concern regarding these, then CE could still do the detection/collecting work, but the submission process would be a manual step for the user to do?
Beta Was this translation helpful? Give feedback.
All reactions