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
I was going through a Vyper bytecode in the playground and I found myself searching for bytecode offsets multiple times in the raw bytecode and in the memory. I had to take the pushed values in hex, convert to decimal, multiply with 2, and use a text editor the find the exact offset for that hex value.
Ideally I should be able to see the byte lengths on selecting with the cursor in bytecode or memory views to see easier.
The CALLER value gets stored to a7 in the memory
Stored:
Later on in the code I want to be able to see the offsets as such
If you think this makes sense, I can implement and open a PR for this, it should be straightforward. We can think about where to show this and the design colors etc. I'd put them bottom right of the memory and bytecode view text blocks, as in the example.
The text was updated successfully, but these errors were encountered:
I was going through a Vyper bytecode in the playground and I found myself searching for bytecode offsets multiple times in the raw bytecode and in the memory. I had to take the pushed values in hex, convert to decimal, multiply with 2, and use a text editor the find the exact offset for that hex value.
Ideally I should be able to see the byte lengths on selecting with the cursor in bytecode or memory views to see easier.
Example
An example with this bytecode
The CALLER value gets stored to
a7
in the memoryStored:
Later on in the code I want to be able to see the offsets as such
If you think this makes sense, I can implement and open a PR for this, it should be straightforward. We can think about where to show this and the design colors etc. I'd put them bottom right of the memory and bytecode view text blocks, as in the example.
The text was updated successfully, but these errors were encountered: