From a01138e1c822b97cf187bfcad9938597bf3edc1e Mon Sep 17 00:00:00 2001
From: nj00001 <42004790+nj00001@users.noreply.github.com>
Date: Mon, 3 Apr 2023 15:32:52 +0800
Subject: fix getOperand out of range

This commit fixes a sloppy function call that should normally check the number of insn's Operand before calling insn's getOperand method. The fix is that if it is 0 it should continue the loop.
I solved problem https://github.com/AFLplusplus/AFLplusplus/issues/1688#issue-1648543691 using this modification
---
 instrumentation/afl-llvm-common.cc | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'instrumentation/afl-llvm-common.cc')

diff --git a/instrumentation/afl-llvm-common.cc b/instrumentation/afl-llvm-common.cc
index dc34d191..de334fb7 100644
--- a/instrumentation/afl-llvm-common.cc
+++ b/instrumentation/afl-llvm-common.cc
@@ -289,6 +289,9 @@ void scanForDangerousFunctions(llvm::Module *M) {
 
     StringRef ifunc_name = IF.getName();
     Constant *r = IF.getResolver();
+    if(r->getNumOperands() == 0){
+      continue ;
+    }
     StringRef r_name = cast<Function>(r->getOperand(0))->getName();
     if (!be_quiet)
       fprintf(stderr,
-- 
cgit 1.4.1