-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[Support] Request including reproduction instructions in bug report message #156958
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
Conversation
@llvm/pr-subscribers-llvm-support Author: Carlos Galvez (carlosgalvezp) Changes… report message Many times people only upload the backtrace without the preprocessed file (or any reproduce), making it difficult to work on the issue. This change syncs the error message with the one in clang/tools/driver/driver.cpp Full diff: https://github.com/llvm/llvm-project/pull/156958.diff 1 Files Affected:
diff --git a/llvm/lib/Support/PrettyStackTrace.cpp b/llvm/lib/Support/PrettyStackTrace.cpp
index 26e22161b605b..2a3903844f9da 100644
--- a/llvm/lib/Support/PrettyStackTrace.cpp
+++ b/llvm/lib/Support/PrettyStackTrace.cpp
@@ -39,7 +39,8 @@ using namespace llvm;
static const char *BugReportMsg =
"PLEASE submit a bug report to " BUG_REPORT_URL
- " and include the crash backtrace.\n";
+ " and include the crash backtrace, preprocessed "
+ "source, and associated run script.\n";
// If backtrace support is not enabled, compile out support for pretty stack
// traces. This has the secondary effect of not requiring thread local storage
|
…essage Many times people only upload the backtrace without reproduction instructions, making it difficult to work on the issue.
68e4c28
to
eb7204c
Compare
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/186/builds/12191 Here is the relevant piece of the build log for the reference
|
Many times people only upload the backtrace without reproduction, making it difficult to work on the issue.