mirror
/
remix-project
mirror of https://github.com/ethereum/remix-project.git
2
0
Fork 0
Code Issues Releases Wiki Activity
remix-project mirror
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2870 Commits
611 Branches
155 Tags
306 MiB
 
 
 
 
 
Tag: Branch: Tree: 894a0abd08
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '894a0abd08'
${ noResults }
remix-project/libs/remix-debugger
History
aniket-engg 894a0abd08
moved libs into libs dir 		4 years ago
..
assets moved libs into libs dir 4 years ago
ci moved libs into libs dir 4 years ago
src/ui moved libs into libs dir 4 years ago
test-browser moved libs into libs dir 4 years ago
README.md moved libs into libs dir 4 years ago
findClient.js moved libs into libs dir 4 years ago
index.html moved libs into libs dir 4 years ago
index.js moved libs into libs dir 4 years ago
nightwatch.js moved libs into libs dir 4 years ago
package-lock.json moved libs into libs dir 4 years ago
package.json moved libs into libs dir 4 years ago
runNode.sh moved libs into libs dir 4 years ago

README.md

remix-debugger

(Remix debugger has been deprecated and is not maintained anymore - the remix-debug module can be used to build your own debugger)

The Remix Debugger is a webapp to debug the Ethereum VM and transactions.

Installation

Make sure Node is installed on your setup, and that a local geth/eth node is running.

git clone https://github.com/ethereum/remix
cd remix/remix-debugger
npm install

This will build the debugger. Start it by opening index.html in your browser.

Development

Run npm run start_dev to start a local webserver, accessible at http://127.0.0.1:8080. Your browser will reload when files are updated.

First steps

Once Remix is connected to a node, you will be able to debug transactions.

You can do that:

  • using a block number and a transaction index.
  • using a transaction hash.

After loading the transaction succeeded, the hash, from and to field will show up. The VM trace is then loaded.

The debugger itself contains several controls that allow stepping over the trace and seing the current state of a selected step:

Slider and Stepping action

The slider allows to move quickly from a state to another.

Stepping actions are:

  • Step Into Back
  • Step Over Back
  • Step Over Forward
  • Step Into Forward
  • Jump Next Call: this will select the next state that refers to a context changes - CALL, CALLCODE, DELEGATECALL, CREATE.

State Viewer

The upper right panel contains basic informations about the current step:

  • VMTraceStep: the index in the trace of the current step.
  • Step
  • Add memory
  • Gas: gas used by this step
  • Remaining gas: gas left
  • Loaded address: the current code loaded, refers to the executing code.

The other 6 panels describe the current selected state:

  • Instructions list: list of all the instruction that defines the current executing code.
  • Stack
  • Storage Changes
  • Memory
  • Call Data$
  • Call Stack

Tests

  • To run unit tests, run npm test.

  • For local headless browser tests:

    • To install selenium: npm run selenium-install
    • Every time you want to run local browser tests, run: npm run test-browser