-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Support generating crash reports. #4863
Labels
bugzilla
Issues migrated from bugzilla
clang:driver
'clang' and 'clang++' user-facing binaries. Not 'clang-cl'
Comments
I wrote up a proposal for this here: |
*** Bug #4621 has been marked as a duplicate of this bug. *** |
I think Chad has implemented this. Further issues w.r.t. crash reporting should |
augusto2112
pushed a commit
to augusto2112/llvm-project
that referenced
this issue
Jun 29, 2022
…object [5.7][lldb] Look through existential types when handling typealiases in SwiftASTContext to correctly handle `AnyObject` existentials.
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bugzilla
Issues migrated from bugzilla
clang:driver
'clang' and 'clang++' user-facing binaries. Not 'clang-cl'
Extended Description
The clang driver should support generating crash reports, to aid development and help users in providing useful feedback.
This is what I envision:
Accept options like -fcrash-report and -fcrash-report=always.
When the driver detects a command failure it attempts to generate a crash report. If -fcrash-report is given instead of -fcrash-report=always then it only does this for "abnormal failures".
Crash reports are generated by creating a new directory in /tmp such as
/tmp/clang-crashreport-X386ysd
which would have the following contents:
a) Contextual information like the environment, path, command line arguments, operating system, versions, etc.
b) The inputs to the driver.
c) The temporary results of the compilation, essentially this is -save-temps if the command is rerun on the inputs inside the crash report directory. The crash report function obviously should notice if the compilation succeeds when it tries to reproduce it.
Provide optional support for reducing the crash report. In general this is probably better done by a clang developer, but reducing the crash report on the client side would solve some problems where the user doesn't want to submit as much data as is in a generic crash report.
Optional autosubmit is overkill. Sweet sweet productivity enhancing overkill.
The text was updated successfully, but these errors were encountered: