-
Notifications
You must be signed in to change notification settings - Fork 9
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
HIGHLY EXPERIMENTAL - Debugger #21
base: main
Are you sure you want to change the base?
Conversation
I was testing out the delve debugger and got a panic in the go runtime.
approx.lisp is in the _examples/sicp/ directory. Then I just run
|
File: fmt.Sprintf("%s", source.Path), | ||
Line: source.Line, | ||
Function: &api.Function{ | ||
Name_: "f", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it not possible to use LEnv.GetFunName here? I noticed this in delve.
(dlv) bt
0 0x0000000000000000 in f
at approx.lisp:5
1 0x0000000000000000 in f
at stream.lisp:5
2 0x0000000000000000 in f
at :0
3 0x0000000000000000 in f
at sicp.lisp:21
4 0x0000000000000000 in f
at sicp.lisp:14
If the function name isn't available might it be better to just use the FID from the stack from?
@bmatsuo-at-luthersystems Personally, I much prefer the JetBrains IDEs to VSCode, but since everyone I know who is using ELPS is using VSCode, I've put 99% of the effort into that. Hence, I've not done as much work on the delve version as the DAP one and would recommend that you use the DAP one - you can use it by running this version of Amir's VSCode extension https://gitlab.com/amirH.A/vscode-elps/-/merge_requests/1/diffs The DAP version is much more stable and does pretty much everything you'd expect a debugger to do. There's a nice video of how to use it floating about - I am pretty sure Sam has it, but if not drop me an email and I'll dig it out for you. |
Needs tidy up and some docs. Just put here for visibility for now.