debuggingemacselispflymake

Is there a trick to debugging a spin in emacs elisp, in a flymake module?

I am getting a CPU spin in emacs elisp, within the C# flymake module. (Flymake is the module in emacs that periodically runs a build, then highlights any syntax errors or warnings in the current buffer.)

I'm about to wade into the code, to look for likely spots where a spin could occur.

While I'm at it, does anyone have suggestions for figuring out the spin? Is there something in emacs that allows me to stop execution and see where it stopped?

Solution

  • Use M-x set-variable to set debug-on-quit to t. Then when the problem happens, hit C-g and the debugger will give you a backtrace of what was running when you stopped it.