assert error in getNonOpaquePointerElementType

[Zzhiter]

Hello, after following the steps of local build and compiling clang, I get an error when running it:

It seems to be a problem with this API?

My LLVM version is release/15.x

[oiiio]

(not a very experienced C/C++ user)

I have tried throwing in some flags like -opaque-pointers=0 but I still get the same error. Bump to this problem

[DavidKorczynski]

Hey! Apologies for the delay here

[DavidKorczynski]

I'll push a fix tonight!

The main reason I didn't do it is that we are rapidly moving to a new frontend that doesn't rely on LLVM LTO. The plan is to deprecate the LTO logic before end of the year, and rely on a pure static (no building) approach. The C logic is more or less ready in https://github.com/ossf/fuzz-introspector/tree/main/frontends/light but we need to get C++ working as well.

[Zzhiter]

May I ask if this problem has been fixed?

[DavidKorczynski]

Apologies for the delay! I'll look at this tomorrow, Friday

[DavidKorczynski]

I'm looking at this now -- does this issue happen when running the build_all.sh script?

Also, which checkout specifically do you use of LLVM? i.e. what do you have on this line?

fuzz-introspector/build_all.sh

Line 59 in 998749b

git checkout llvmorg-18-init-14420-gea3a3b25

[Zzhiter]

Thank you! No, I meet this issue when following the LocalBuild:

I use 939f5a33711370697f9ad1de4267cfc7399dfe86 commit of LLVM, which is release/15.x.

[AnnabellaM]

I also ran into the same error when I was following the installation instructions on this webpage https://fuzz-introspector.readthedocs.io/en/latest/installation-instructions/installation.html. The same error occurred when I ran this command FUZZ_INTROSPECTOR=1 ../../../build/llvm-build/bin/clang -fsanitize=fuzzer \ -fuse-ld=gold -flto -g ../fuzzer.c -o fuzzer

[DavidKorczynski]

@Zzhiter can you confirm which checkout specifically do you use of LLVM? i.e. what do you have on this line

fuzz-introspector/build_all.sh

Line 59 in 998749b

git checkout llvmorg-18-init-14420-gea3a3b25

?

Nvm, I see you mention the commit now, thanks!