Assertion !syscall_bp_vm failed to hold during replay
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Similarly to #2286 and #2292.
I can hit this reliably running llvm/llvm-project clang @ master, but unfortunately I'm going away for a few weeks now. I've run out of time but trying to put as much information here as I can. Notably, gdb has a problem with what I'm doing too.
I'm invoking the clang frontend and trying to put a breakpoint on clang::ExecuteCompilerInvocation, then single step into it.
LLVM/Clang is built with -DBUILD_SHARED_LIBS -DLLVM_USE_SPLIT_DWARF=On CMAKE_EXE_LINKER_FLAGS:STRING='-Wl,-gdb-index -fuse-ld=lld '.
Interestingly, gdb also crashes if I try to step through this call. The call itself shows up as clang::ExecuteCompilerInvocation@plt during the breakpoint.
If I get time I'll try and add more information, but no promises! I hope there is something useful in what I have written above.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with llvm/llvm-project clang at master, built with the stated shared-library, split-DWARF, linker, and gdb-index options. Set a breakpoint on clang::ExecuteCompilerInvocation and single-step into it during replay, comparing the behavior with gdb. Done means the !syscall_bp_vm assertion is understood and the replay no longer fails in this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100