Re: [O] Emacs sagmentation fault error on a big org-mode file movement

2017-12-17 Thread numbch...@gmail.com
I'm doing it try to reproduce this sagment fault. but can't reproduce it for now. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.gi

Re: [O] Emacs sagmentation fault error on a big org-mode file movement

2017-12-16 Thread Neil Jerram
I would suggest (but without detailed knowledge of current emacs practice): 1. Report your exact emacs version. 2. Install a corresponding debug symbols package, if your distro provides that.  That should add a lot more interesting detail to the backtrace. 3. To go further, repro under GDB,

Re: [O] Emacs sagmentation fault error on a big org-mode file movement

2017-12-16 Thread numbch...@gmail.com
That's very helpful . Thanks very much. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Sat, Dec 16, 2017 at 4:38 PM,

Re: [O] Emacs sagmentation fault error on a big org-mode file movement

2017-12-16 Thread Eli Zaretskii
> From: "numbch...@gmail.com" > Date: Sat, 16 Dec 2017 12:27:58 +0800 > > Is there a way to debug this? Run Emacs under a debugger, trigger the crash, and produce a more helpful backtrace by typing the "bt" command at GDB prompt. Please report all of that to the Emacs issue tracker using the co

[O] Emacs sagmentation fault error on a big org-mode file movement

2017-12-15 Thread numbch...@gmail.com
I have a big org-mode file which is overview at startup. When I navigate around with [C-v] and [M-v]. The Emacs crashed. Here is the output from command-line: ``` Fatal error 11: Segmentation fault Backtrace: emacs[0x51195e] emacs[0x4f739a] emacs[0x50fe3e] emacs[0x510058] emacs[0x5100dc] /usr/lib/