You are not logged in.
Pages: 1
For some days I opened this issue (https://bbs.archlinux.org/viewtopic.php?id=195913) which I closed myself, because I thougt it was solved. But it isn't. I'm experiencing emacs crashes. I think (but I am not sure) this began with the last big update of gtk3.
I compiled emacs with debug options and got now this backtrace (http://pastie.org/10111821). Can anyone interpret this? Or should I ask the emacs people?
I can not manage to reproduce exactly the crash, but it always happens when I save a buffer in a console in which I open a emacsclient with emacsclient -nw...
Many thanks in advance!
Offline
Ah, you use [multilib]. I think from the backtrace this should go to the Arch Linux bugtracker.
Offline
good, thanks. I will wait til I have a better backtrace...
Offline
Hi rogorido,
by any chance is your cpu an Intel Haswell?
If it is, try to update the microcode https://wiki.archlinux.org/index.php/Microcode
Offline
Hi rogorido,
by any chance is your cpu an Intel Haswell?
If it is, try to update the microcode https://wiki.archlinux.org/index.php/Microcode
Thanks for your answer, but no. I have AMD.
What is the best way to compile emacs with all debug info enabled?
Last edited by rogorido (2015-04-29 13:45:34)
Offline
What is the best way to compile emacs with all debug info enabled?
Take a look at the wiki, it is described quite well https://wiki.archlinux.org/index.php/De … ing_Traces.
Offline
rogorido wrote:What is the best way to compile emacs with all debug info enabled?
Take a look at the wiki, it is described quite well https://wiki.archlinux.org/index.php/De … ing_Traces.
Yes, it is described quite well, but I dont get really useful debug traces with emacs...
Offline
Pages: 1