warning medusa init

[s4nsec]

• Move CallFrame to utils
• Add ValueGenerationTracer
• Import CallFrame from utils for execution_tracer
• Initialize ValueGenerationTracer in fuzzer_worker.go
• Add a unit test for ValueGenerationTracer
• Enable ValueGenerationTracer in configs
• Enable ValueGenerationTracer in medusa.json
• Modify existing contract to fit our test case
• Add necessary functions to get event values
• Add captureEnteredCallFrame in CaptureEnter
• grab events
• make generating events a ValueGenerationTrace capability
• Change emitted event values to check for changes in valueSet
• Store captured event values and their types in a data structure and add them to valueSet
• Remove SetValueSet function
• Modify assert_immediate.sol to check return value collection functionality
• Modify fuzzer configs to make debugging easier
• Remove deprecated storage alternatives for event values
• Provide a new structure to store both event and return values
• Get return value of the current call frame
• Call getCallFrameReturnValue from captureExitedCallFrame
• Provide collected event and return values to MessageResults
• Write colleced transaction output values(return, event data) to current sequence value set
• Use AddTransactionOutputValuesToValueSet in fuzzer worker
• Rename ValueGenerationTracingEnabled parameter to ExperimentalValueGenerationEnabled
• Modify the logic to preserve base value set
• Set TransactionOutputValues to []any
• Perform modifications on ValueGenerationTracer methods to adapt to new structure for holding emitted and return values
• Emit and return values of various types
• Add a test to check if base value set is preserved throughout the fuzzing campaign
• Move ExperimantalValueGenerationEnabled to TestingConfig
• Fix overwriting return values with event values issue
• Use eventOrReturnValue as variable name to avoid ambiguity
• Grab only if ReturnError is nil
• Don't expect values when it is contract creation
• Move ExperimentalValueGenerationEnabled to TestingConfig
• Remove type TransactionOutputValues
• Add comment descriptions to ValueGenerationTracer members
• Remove stale comments and print statements
• Prevent return values from being reset
• Make adding transaction output values value_set.go's responsibility
• Use Add instead of deprecated AddTransactionOutputValuesToValueSet
• Use fw.fuzzer.config.Fuzzing.Testing.ExperimentalValueGenerationEnabled
• Check whether all values are added and if the base value set is preserved
• Reset assert_immediate.sol to default
• Add a contract to test event and return value collection
• Add to value set inside the unit test
• Adapt value generation tracer to interface changes
• Prompt to overwrite config file

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

:white_check_mark: s4nsec
:white_check_mark: anishnaik
:x: Sanan Hasanov

---

Sanan Hasanov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}