>> I confirm this -- running 25.1+1-2 on amd64, I get the exact same backtrace:
> If you get a chance, could you try 25.1+1-3 and see if it behaves
> better? Hopefully it has fixed a problem with the choice of allocator
> which might be related.
It hasn't crashed yet.
Juliusz Chroboczek writes:
> I confirm this -- running 25.1+1-2 on amd64, I get the exact same backtrace:
If you get a chance, could you try 25.1+1-3 and see if it behaves
better? Hopefully it has fixed a problem with the choice of allocator
which might be related.
Thanks
--
Rob Browning
rlb
I confirm this -- running 25.1+1-2 on amd64, I get the exact same backtrace:
Backtrace:
emacs[0x50b89c]
emacs[0x4f1c5c]
emacs[0x50a00e]
emacs[0x50a239]
emacs[0x50a29f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11100)[0x7f2b00e2b100]
emacs(re_search_2+0x3a8)[0x542908]
Package: emacs25
Version: 25.1+1-2
Severity: normal
I have been running emacs25 for a day or two and have already had 3 crashes.
The last crash happened when I was simply typing in a buffer.
Backtrace:
emacs[0x50b89c]
emacs[0x4f1c5c]
emacs[0x50a00e]
emacs[0x50a239]
emacs[0x50a29f]
/lib/x86_64-lin
4 matches
Mail list logo