search

Quuxplusone / LLVMBugzillaTest

0 stars 0 forks source link

Crash reporting should be extensible with an external tool #13235

Open Quuxplusone opened 12 years ago

Quuxplusone commented 12 years ago
Bugzilla Link PR13150
Status NEW
Importance P enhancement
Reported by Chandler Carruth (chandlerc@gmail.com)
Reported on 2012-06-19 13:16:24 -0700
Last modified on 2012-06-20 15:33:20 -0700
Version unspecified
Hardware Other All
CC bob.wilson@apple.com, chad.rosier@gmail.com, chandlerc@gmail.com, daniel@zuster.org, llvm-bugs@lists.llvm.org
Fixed by commit(s)
Attachments
Blocks
Blocked by
See also 
The idea is that anyone distributing Clang could ship an external tool that
does automatic bug triage / reporting, or integrates with crash reporting on
the host OS etc.

It would be important to continue to do most of the crash handling in the
driver where we know about Clang, and the command, and can build up the proper
reproduction steps, and then to hand all that information off to the separate
tool if it exists, or report it (much as we already do) to the user.
Quuxplusone commented 12 years ago

I went ahead and cloned this to rdar://problem/11703974 to ease trackability. However, I've indicated in the radar we should make comment here to solicit feedback from the community.

Quuxplusone commented 12 years ago

Bob [Wilson] made a very good point. The preprocessed source of an external developer's code exposes their proprietary information. We want to make it easy for them to submit that source but it has to be a voluntary step. Thus, we really can't automate the entire process.