is it blank all the time for this contract? Or just in some sections?

is it blank all the time for this contract? Or just in some sections?

Just some sections.

I get this a lot as well, sometimes in very large blocks.

Similar reproduction steps:

1. Clone this repo: https://github.com/tcoulter/sai
2. Run dapp debug
3. Choose the test CageTest::testCageExistAfterPeriod() (it happens frequently there, though you'll likely reproduce it with many of these tests)
4. Press n to step through until you see the same error as the OP.

From my experience, it seems related to contract creation, as it appears to happen a lot during the non-constructor code related to contract creation. This is only a hunch however.

As a feature request, it'd be great if I could step over anything unknown.

Environment:

• Windows Subsystem for Linux v2 (Ubuntu 20.04.1 LTS)
• dapp 0.33.0
• solc, the solidity compiler commandline interface
• Version: 0.8.6+commit.11564f7e.Linux.g++
• hevm 0.47.0

As a feature request, it'd be great if I could step over anything unknown.

you can step to the next piece of source code with shift-N, or step forward through the bytecode without entering subcalls with control-n

In the case above, I do use shift-N. When it reaches anything unknown, it steps through the instructions as if I was just pressing N alone.

Edit: I guess I didn't specify that above. Perhaps that's a bug!

In the case above, I do use shift-N. When it reaches anything unknown, it steps through the instructions as if I was just pressing N alone.

Edit: I guess I didn't specify that above. Perhaps that's a bug!

yup same. should have specified as well oop 😅

doesn't feel good to be stepping thru things smoothly with N and then hit a 2 second patch of abyss

@MrChico @d-xo bumping because running into this while debugging some complex tests rn and its slowing me down quite a bit heh

Not sure we can do much about the fact that srccode is missing for parts of the code, but we can fix the N and c-n issue

but we can fix the N and c-n issue

yup, thats what i was hoping for 🙏

btw i dont see this issue with c-n, but i do sometimes see with c-p

bump hehe

hehe i just want the debugger to skip the Nothing (?) screens when stepping thru with shift + N/shift + P

@transmissions11 had been kinda avoiding this one since the source map parser and format are quite mysterious to me 🙈, think I have a fix, would be great if you could test it out.