[llvm] Reland [llvm] Errorize DebuginfodFetcher for inspection at call-sites (PR #194872)
Stefan Gränitz via llvm-commits
llvm-commits at lists.llvm.org
Wed May 6 02:08:01 PDT 2026
weliveindetail wrote:
Ok, thanks. Yes, forcing the curl feature is what I had to do as well and the result looks similar. However, that is not the problem we saw downstream originally.
@gulfemsavrun I don't see how your bot arrived at the stated point of failure in llvm-profdata:
https://luci-milo.appspot.com/ui/p/fuchsia/builders/toolchain.ci/clang-linux-x64/b8683909703278781009/test-results
```
# .---command stderr------------
# | Failure value returned from cantFail wrapped call
# | No such file or directory
# | UNREACHABLE executed at llvm/include/llvm/Support/Error.h:779!
# | PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace and instructions to reproduce the bug.
# | Stack dump:
# | 0. Program arguments: llvm-profdata merge -o /b/s/w/ir/x/w/llvm_build/runtimes/runtimes-x86_64-unknown-linux-gnu-bins/compiler-rt/test/profile/Profile-x86_64/Output/instrprof-binary-correlate-debuginfod.c.tmp.correlate-debuginfod.profdata --debuginfod --correlate=binary /b/s/w/ir/x/w/llvm_build/runtimes/runtimes-x86_64-unknown-linux-gnu-bins/compiler-rt/test/profile/Profile-x86_64/Output/instrprof-binary-correlate-debuginfod.c.tmp.correlate.profraw
# | #0 0x0000559519f92178 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/b/s/w/ir/x/w/llvm_build/bin/llvm-profdata+0x61c178)
# `-----------------------------
# error: command failed with exit status: -6
```
We cannot reproduce it and the stacktrace contains only the last frame. Any chance you could give this a try again and post an actual stacktrace in case it still fails? Thanks 🙏
https://github.com/llvm/llvm-project/pull/194872
More information about the llvm-commits
mailing list