-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forge debug
does not have source view
#5569
Comments
Noting that this has already been raised in #5435 Also noting that this is a major headache 😔 |
Yep @jameswenzel — I'll try to make time between tomorrow and friday to look into this so we can unblock u and more ppl on the support channel! Let's close this issue and keep tracking on #5435 |
Right @iFrostizz ! That'd be awesome if the refactor fixed it. A quick fix for this would also be appreciated for this if you know the cause! |
If there's a refactor y'all might find Debug Adapter Protocol interesting; lets people use VSCode/Vim/whatever as the frontend. I don't think the VSCode UI is necessarily that much better, if at all, but idk, using standard framework could turn out to be easier to build/maintain Example, rust-analyzer has a pretty nifty CodeLens (although they may switch to VSCode-specific API) for debug test which I believe passes off to DAP (e.g. lldb): |
You might wanna try my branch #5547 tho the source mapping may be incorrect |
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (1a110a5 2023-08-08T16:26:20.836709000Z)
What command(s) is the bug in?
forge debug
Operating System
macOS (Apple Silicon)
Describe the bug
Create file
contracts/Counter.sol
: https://solidity-by-example.org/first-app/Run:
forge debug --debug contracts/Counter.sol --sig "inc()"
Result:
The text was updated successfully, but these errors were encountered: