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, ideally with corresponding source
code. Then you could explore the immediate cause of the segfault.
Neil
On 16/12/17 04:27, numbch...@gmail.com wrote:
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/libpthread.so.0(+0x11da0)[0x7fcb1cdcada0]
emacs[0x4caa74]
emacs[0x45b2b5]
emacs[0x4613e9]
emacs[0x41eb42]
emacs[0x42087c]
emacs[0x42157a]
emacs[0x421567]
emacs[0x421567]
emacs[0x42351d]
emacs[0x458015]
emacs[0x501893]
emacs[0x50465a]
emacs[0x5061dc]
emacs[0x56c85e]
emacs[0x4f7754]
emacs[0x56c7cd]
emacs[0x4f76eb]
emacs[0x4fc313]
emacs[0x4fc636]
emacs[0x41b302]
/usr/lib/libc.so.6(__libc_start_main+0xea)[0x7fcb1bf30f4a]
emacs[0x41c01a]
[1] 17259 segmentation fault (core dumped) emacs --debug-init
```
Is there a way to debug this?
I know it is not possible to invoke edebug on anything internal Emacs.
So is there any system (Linux) solution?
Like system process dump or traceback.
I'm using latest version `master` branch source code Org-mode.
Emacs is from compiled `master` branch source code too.
[stardiviner] <Hack this world!> 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/
