You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thread 'main' panicked at 'internal error: entered unreachable code', analyzer/src/traversal/functions.rs:379:5
stack backtrace:
0: rust_begin_unwind
at /rustc/c0b64d97beebb09325b5587abed39f4f1621026f/library/std/src/panicking.rs:493:5
1: core::panicking::panic_fmt
at /rustc/c0b64d97beebb09325b5587abed39f4f1621026f/library/core/src/panicking.rs:92:14
2: core::panicking::panic
at /rustc/c0b64d97beebb09325b5587abed39f4f1621026f/library/core/src/panicking.rs:50:5
3: fe_analyzer::traversal::functions::traverse_statements
4: fe_analyzer::traversal::functions::func_body
5: fe_analyzer::traversal::contracts::contract_def
6: fe_analyzer::traversal::module::module
7: fe_analyzer::analyze
8: fe_compiler::compile
9: fe::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Aborted
agroce
changed the title
internal error: entered unreachable code at semantics/src/traversal/functions.rs:383:5
internal error: entered unreachable code at analyzer/src/traversal/functions.rs:379:5
Feb 17, 2021
Compiling this file:
On latest github master, built with
for fuzzing. Using https://github.com/agroce/afl-compiler-fuzzer (we've found more than 50 bugs (that were worth fixing, and have been fixed) in solc using this afl variant) + afl.rs.
This might be a more interesting type of bug, if you think fe is ready for fuzzing at all.
The text was updated successfully, but these errors were encountered: