Medusa ForkMode causes crashes when trying to run a second instance of Medusa #635
Description
When trying to run more than one instance of Medusa in fork mode, the second medusa instance will crash after compilation
medusa-rpc % medusa fuzz
⇾ Reading the configuration file at: /Users/cerberus/Desktop/Consulting/medusa-rpc/medusa.json
⇾ Compiling targets with crytic-compile
⇾ Running command:
/opt/homebrew/bin/crytic-compile . --export-format solc --foundry-compile-all
⇾ Finished compiling targets in 5s
⇾ Using cached Slither results found at slither_results.json
⇾ Initializing corpus
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x30 pc=0x10510491c]
goroutine 1 [running]:
github.com/crytic/medusa/fuzzing.(*Fuzzer).createTestChain(0x1400029d008)
github.com/crytic/medusa/fuzzing/fuzzer.go:454 +0x38c
github.com/crytic/medusa/fuzzing.(*Fuzzer).Start(0x1400029d008)
github.com/crytic/medusa/fuzzing/fuzzer.go:813 +0x524
github.com/crytic/medusa/cmd.cmdRunFuzz(0x105d9c520, {0x105e543c0?, 0x4?, 0x105208e82?})
github.com/crytic/medusa/cmd/fuzz.go:168 +0x774
github.com/spf13/cobra.(*Command).execute(0x105d9c520, {0x105e543c0, 0x0, 0x0})
github.com/spf13/[email protected]/command.go:1015 +0x828
github.com/spf13/cobra.(*Command).ExecuteC(0x105d9bfa0)
github.com/spf13/[email protected]/command.go:1148 +0x350
github.com/spf13/cobra.(*Command).Execute(...)
github.com/spf13/[email protected]/command.go:1071
github.com/crytic/medusa/cmd.Execute()
github.com/crytic/medusa/cmd/root.go:30 +0x60
main.main()
github.com/crytic/medusa/main.go:12 +0x1cSee example:
https://github.com/GalloDaSballo/medusa-rpc-crash-repro
Just plug your RPC and run 2 instances for repro