[BUG] Segmentation Fault when Beaconfuzz_v2 targets Struct_block

[Daft-Wullie]

Description

Beaconfuzz_v2 is currently unable to fuzz the struct_block target as it immediately segfaults.

Expected Behavior

Beaconfuzz_v2 should start fuzzing the specified target.

Actual Behavior

a Segmentation Fault occurs

Possible Fix

N/A

Steps to Reproduce

ETH2FUZZ_BEACONSTATE=../eth2fuzz/workspace/corpora/beaconstate fuzz/target/x86_64-unknown-linux-gnu/release/struct_block -artifact_prefix=/home/beacon-fuzz/beaconfuzz_v2/fuzz/artifacts/struct_block/ /home/beacon-fuzz/beaconfuzz_v2/fuzz/corpus/struct_block -detect_leaks=0 -rss_limit_mb=0

Your Environment

• Version/Commit used: a990138
• Operating System and version: Ubuntu 20.04

[pventuzelo]

I confirm, I got the same.
it is maybe related to Consensys/teku#3125

I will investigate.

[ajsutton]

Consensys/teku#3125 looks like some form of JVM bug (can't be 100% certain and not sure how to reproduce it yet) but it has the distinctive property that it's always crashing in one of the native methods related to getting thread info. Often this is while acquiring a lock as they check ThreadLocal variables to provide reentrancy support but can be from a few things. Java will typically produce a full report in a hs_err file which I can look at if you have one and see if it looks similar.