1

I am GNU Emacs 28.1.91 with native compilation. Emacs freezes so often, where I am unable to find what's is wrong. During the freeze all my work is always gone where the save does not occur.

Following: What do I do when Emacs is frozen? [duplicate], I have done M-x toggle-debug-on-quit. but when freeze happens I cannot see/reach *Backtrace* of the error. I have to restart the Emacs and I cannot reach the log :-(

Is possible to write the log the bactrace to a file?

alper
  • 1,370
  • 1
  • 13
  • 35
  • Keep *Backtrace* visible in another frame? – Gilles 'SO- stop being evil' Oct 06 '22 at 21:56
  • I am using Emacs daemon when I keep Backtrace visible I cannot get back focus to the buffer I am working on. – alper Oct 06 '22 at 22:14
  • Which version of Emacs are you using? – phils Oct 07 '22 at 00:51
  • @phils GNU Emacs 28.1.91 with native compilation – alper Oct 07 '22 at 09:04
  • Can't you resize the frames and keep them both visible at the same time? – NickD Oct 07 '22 at 16:26
  • @NickD I have tired that but when I cannot do M-x <funcname> on a different tab, the focus switch into backtrace frame – alper Oct 07 '22 at 19:26
  • Maybe forego native compilation for now? It may be too new to use on your "working" emacs session. Maybe use it only for playing around, testing and reporting bugs and revert to a "normal" Emacs for your work. – NickD Oct 07 '22 at 19:34
  • @NickD After countless tries I was able to capture a debug output related jit-lock-force-redisplay as follows: https://gist.github.com/avatar-lavventura/85e5222f3e01760f96b82b85f7929cbb?permalink_comment_id=4330313#gistcomment-4330313 // I am not sure would this help to find the problem. – alper Oct 10 '22 at 16:34

0 Answers0