Crashes on breakpoint (Python) about dap-mode HOT 5 CLOSED

Can you confirm that you are getting the same with M-x lsp-start-plain?

cc @Alexander-Miller

from dap-mode.

@yyoncho Thanks for quick answer.

Turns out I did not. I'm not so familiar yet with the debugger, but it looks like it worked.

I had to manually eval
(require 'dap-python)
(setq dap-python-debugger 'debugpy)

But after that it seemed to work with default settings.

The way I updated packages was list-packages -> update all. Maybe I should try deleting the elpa directory and try again?

from dap-mode.

The way I updated packages was list-packages -> update all. Maybe I should try deleting the elpa directory and try again?

Update all is usually not the best way to update because it may cause issues. The best way to upgrade is to delete the packages to update, restart emacs, and install them in clean session.

from dap-mode.

@yyoncho Thank you, deleting the elpa folder and installing everything again seemed to work. (aside: is there no better way to update packages?)

Now I just need to learn the interface :)

from dap-mode.

is there no better way to update packages?

I think that package-utils-upgrade-all-and-recompile from package-utils package but I am not 100% sure. It was a method from path package. The issue here is that when you upgrade in the current session then you end up with packages being compiled with the packages that are already loaded. E g. if you have 2 packages to upgrade A and B and A depends on B you may end up with A being compiled against old B because old B is already loaded. FWIW spacemacs default upgrade package functionality is doing exactly that: It deletes the packages to upgrade, restarts emacs and install them in clean session.

from dap-mode.