godotengine / godotengine/emacs-gdscript-mode

Debugging isn't how the readme describes

Open
#212 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Emacs Lisp
Stars
401
Forks
42
Avg merge
23h 23m
Merged PRs (30d)
1

Description

I'm using godot 3.6 and vanilla emacs and the debugger doesn't behave like how the readme says it should.
When I hit a breakpoint, neither an inspector buffer nor a stack frame buffer are displayed. I can get to them through the debug hydra but they are empty.
Instead I get a very simple debug prompt.
Image

The debug hydra can show the other buffers but can not step forward or continue, it simply says that no game process is running while the prompt is still able to do these things.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the README's debugging instructions with the reported behavior in Godot 3.6 and vanilla Emacs. Reproduce a breakpoint, inspect the debug hydra and simple debug prompt, and determine why the inspector and stack-frame buffers are empty and why hydra controls report no game process. Done means the documented debugging flow and controls work consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
emacs, emacs-lisp, godot
Domain
devtools, game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.