This repository was archived by the owner on Nov 25, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 160
bug: inspect databases #1137
Copy link
Copy link
Labels
bugSomething isn't workingSomething isn't working
Description
Currently, enabling the inspect-database option in Coreth results in VM initialization erroring. I first noticed this bug here: https://github.com/ava-labs/avalanchego/actions/runs/17109691592/job/48527748332?pr=4190#step:4:1158
Code Path/Steps To Reproduce:
- Prior to starting up the VM, make sure that the
inspect-databaseoption in the EVM config is set totrue[ref] - In
Initialize()[ref], we create the VM databases includingchainDBwhich is instantiated as follows:vm.chaindb = rawdb.NewDatabase(database.WrapDatabase(prefixdb.NewNested(ethDBPrefix, db)))[ref]. Note thatvm.chainDBis wrapped in thenofreezedbtype - Since we specified
inspect-databasetotrue, we callinspectDatabases()[ref] - In
inspectDatabases(), we callrawdb.InspectDatabases()onvm.chainDBwhich eventually inspects the DB freezers [ref]. - The freezer inspection code eventually calls one of the methods of
chainDB, which results in the errorerrNotSupportedbeing returned [ref].
This error occurs because in Coreth, we do not utilize a freezer database while geth does.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working