Repository navigation
verify: Send crash reports to cpp-verify's issue tracker - #46
Merged
Merged
Conversation
This was referenced Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A crash of
cpp-verify, or of theclangit is built with, asked for a report on LLVM's issue tracker:Those reports belong to this repository.
PACKAGE_BUGREPORTinllvm/CMakeLists.txt, the default of theBUG_REPORT_URLcache variable that bothllvm/Config/config.handclang/Config/config.htake, now nameshttps://github.com/SwayamInSync/cpp-verify/issues/. LLVM's stack-trace handler and the Clang driver both print it.A build directory configured before this keeps LLVM's address in its CMake cache, because
BUG_REPORT_URLis a cache variable;cmake -UBUG_REPORT_URL <build>picks up the new default. CI and release builds configure fresh.Docs: the tooling page gains a section on what a crash prints, what to include in a report, and the stale cache. The release notes get an entry under "Running cpp-verify".
Testing:
Verify/crash_report_url.cppcrashescpp-verifyandclang -cc1with#pragma clang __debug crashand checks the address. It usesnot --crashandREQUIRES: crash-recovery, backtrace, as Clang's crash tests do;not --crashalready treats an abort on Windows as a crash. Both lines fail on main's binary.clang++from the same build prints the address too. Clang's crash-report tests, which match the address with{{.*}}, still pass (Driver/crash-report*.{test,m,cpp},Driver/crash-diagnostics-tar.c,Analysis/crash-trace.c;crash-report-crashfile.mis Darwin-only). The documentation examples pass and the site builds with-W.