-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Attempts to start debugging result in error Cannot evaluate 'execAddress' #110
Comments
There're currently some severe problems with the 3.2.2 version. |
I just released 3.2.3 to the market place. Please let me know if the problem persists. |
OK. No need to do any further tests.
DEVICE NOSLOT64K
test_main:
RET
Will work on a solution. Meanwhile please use '"exec_address:" 0'. |
Please try this fix: |
Thank you. A workaround I found is to set exec address to 0x0000 (or any hex address, instead of a label), save, run, then change back to the label, save and run. I will upgrade to 3.2.3 shortly. I appreciate the support. |
I upgraded to 3.2.3 from the Marketplace and still have the same issue. |
You need to upgrade to 3.2.3-rc1 that I attach few comments above. Unzip and 'Install from vsix...". |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A debugging session starts with the PC initialised to test_main
Screenshots

Version etc. (please complete the following information):
Notes:
The text was updated successfully, but these errors were encountered: