-
Notifications
You must be signed in to change notification settings - Fork 181
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
dap-ui-debug-window: Symbol’s function definition is void: debug-window-mode #8
Comments
Regarding the
|
I have pushed a fix for the sessions, you may eval the function bellow or wait for the melpa. The handling for missing sources was broken after python integration.
(defun dap-ui--stack-frames (thread-tree)
"Method for expanding stackframe content.
THREAD-TREE will be widget element holding thread info."
(let* ((session (widget-get thread-tree :session))
(thread (widget-get thread-tree :thread))
(thread-id (gethash "id" thread))
(stack-frames (gethash thread-id (dap--debug-session-thread-stack-frames session))))
(if stack-frames
;; aldready loaded
(mapcar (-lambda ((stack-frame &as &hash "name" "line" "source"))
(let ((tag (if source
(format "%s (%s:%s)"
name
(or (gethash "name" source)
(gethash "path" source))
line)
(format "%s (Unknown source)" name))))
`(tree-widget :tag ,tag
:format "%[%t%]\n"
:stack-frame ,stack-frame
:session ,session
:element-type :stack-frame
:thread ,thread
:dynargs dap-ui--stack-frames
:open nil)))
stack-frames)
(when (and (string= (gethash thread-id (dap--debug-session-thread-states session)) "stopped")
(widget-get thread-tree :loading))
(widget-put thread-tree :loading t)
(dap--send-message
(dap--make-request "stackTrace"
(list :threadId thread-id))
(dap--resp-handler
(lambda (stack-frames-resp)
(with-current-buffer dap-ui--sessions-buffer
(let ((stack-frames (or (-some->> stack-frames-resp
(gethash "body")
(gethash "stackFrames"))
(vector))))
(puthash thread-id
stack-frames
(dap--debug-session-thread-stack-frames session))
(tree-mode-reflesh-tree thread-tree)
(run-hook-with-args 'dap-ui-stack-frames-loaded session stack-frames)))))
session))))) |
Have a remote debug session against Tomcat going,
dap
stops at my break point and I can see the locals withdap-ui-locals
. So far so good.However, I'd like to see the threads so that I can step back in the call stack, I therefore tried out the different
dap-ui-*
methods in the hope that one of these would give me the thread view I'm familiar with from other IDEs, however:yielded only:
On a related question: I would expect
dap-mode
to open default/configuredap-ui
windows either when you first calldap-debug
or at the latest, when the code hits a breakpoint. Right now, I'm fumbling a bit in the dark.Versions:
The text was updated successfully, but these errors were encountered: