Cope with MCOperand null Insts #91794
Merged
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.
I encountered a bolt segfault due to an MCOperand of type Inst with a null pointer. It seems bolt is intentionally creating such operands, so it would be good for the printer to not barf on them.
The bolt code is bolt/include/bolt/Core/MCPlusBuilder.h where the annotation machinery is. For example line 131 in setAnnotationOpValue:
Inst.addOperand(MCOperand::createInst(nullptr));
In my case it was annotating an X86 JCC instruction, and using --debug crashed.