This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Radar · Solidity · Archive · Week 42 · Oct 13 – 19, 2025

ethdebug: Experimental EOF support

Nice to knowtooling

What changed
The ethdebug tool now experimentally supports instructions and source locations under EOF.
Production impact
The source does not say.
Try it
Run ethdebug on an EOF contract and check that source locations are reported.
Source
github.com/argotorg/solidity/releases/tag/v0.8.31-pre.1

Understand it, then run it

The ethdebug tool now can show where in the source code each instruction comes from when you debug contracts that use the new EOF format. EOF, or “EVM Object Format,” is a new way to package bytecode that can contain multiple “sub‑contracts” in one file. Before this change, ethdebug could only map instructions back to the original Solidity source for regular contracts. With the update, if you compile a contract to EOF, the debugger will still point you to the exact line in your Solidity file that produced each bytecode instruction.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed