-
Notifications
You must be signed in to change notification settings - Fork 50
test: Add test for debug locations #810
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
base: next
Are you sure you want to change the base?
Conversation
|
Similar situation is when an |
Interesting. I see we set the passed
I wonder how it ends up being lost. Or do we pass an empty span here? Any ideas? EDIT: Oh, I'm just slow. #812 (comment) fixes it, right? |
|
I double checked now, without changes from #812 (comment) (so basically with this branch only), we have this situation: As you can see Here is the fix 0xMiden/miden-vm#2449. So, only with this fix (we can completely forget about #812 for now), we see: But, for the test I added here, the |
|
So we have source location for the panic function call but no source code for the unreachable op inside it. I wonder if miden-debug could go up the stack and find the first source span. But it would not help when we're running in the VM through the miden-client. So whatever solution we find needs to be implemented in the VM. |
|
@djolertrk good catch! Great job! |
This demonstrates that simple "assert-based debugging" does not work.
The reason is that there is no source locations attached to
ub.unreachable.It can be confirmed by using following commands:
And to run the integration test:
This addresses #806.