Skip to content
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

Closed
llvmbot opened this issue Jul 1, 2009 · 3 comments
Closed

Support generating crash reports. #4863

llvmbot opened this issue Jul 1, 2009 · 3 comments
Labels
bugzilla Issues migrated from bugzilla clang:driver 'clang' and 'clang++' user-facing binaries. Not 'clang-cl'

Comments

@llvmbot
Copy link
Member

llvmbot commented Jul 1, 2009

Bugzilla Link 4491
Resolution FIXED
Resolved on Jun 13, 2012 13:23
Version unspecified
OS All
Reporter LLVM Bugzilla Contributor

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:

  1. Accept options like -fcrash-report and -fcrash-report=always.

  2. 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".

  3. 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.

  4. 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.

  5. Optional autosubmit is overkill. Sweet sweet productivity enhancing overkill.

@llvmbot
Copy link
Member Author

llvmbot commented Jul 31, 2010

I wrote up a proposal for this here:
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-July/009903.html

@llvmbot
Copy link
Member Author

llvmbot commented Jul 31, 2010

*** Bug #4621 has been marked as a duplicate of this bug. ***

@chandlerc
Copy link
Member

I think Chad has implemented this. Further issues w.r.t. crash reporting should
be new bugs.

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'
Projects
None yet
Development

No branches or pull requests

2 participants