search

crytic / medusa

Parallelized, coverage-guided, mutational Solidity smart contract fuzzing, powered by go-ethereum
https://secure-contracts.com/program-analysis/medusa/docs/src/
GNU Affero General Public License v3.0
301 stars 40 forks source link

Add verbosity levels to logging #204

Open anishnaik opened 1 year ago

anishnaik commented 1 year ago

Currently, the execution traces on failed tests can be quite aggressive for more complex systems where we enter into multiple call frames within a single call. Thus, we should introduce various verbosity levels that can allow the user to choose what they want the log output to look like.

I propose the following log levels:

  1. -v: Test results are shown. No execution traces or console.log events are shown
  2. -vv: Top-level call frame execution traces as well as console.log events are shown for failing tests
  3. -vvv: TBD
  4. -vvvv: TBD

edit (Jan 31, 2023): There should also be the capability to disable tracing all together (#149 )

rappie commented 3 weeks ago

I would love to see this implemented. My current project has a trace of more than 5000 (!) lines, it's a huge pain to keep scrolling up while debugging :sweat_smile: