From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Jerram Subject: Re: Emacs sagmentation fault error on a big org-mode file movement Date: Sat, 16 Dec 2017 10:58:36 +0000 Message-ID: <00d6f98c-31b2-fd9e-e4af-e6d9445d8945@ossau.homelinux.net> References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------CEA8F5085777CF6F5394EE02" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48944) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eQAB4-0007dk-Ts for emacs-orgmode@gnu.org; Sat, 16 Dec 2017 05:58:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eQAB0-0002t7-Us for emacs-orgmode@gnu.org; Sat, 16 Dec 2017 05:58:46 -0500 Received: from smtp-out-3.talktalk.net ([62.24.135.67]:57289) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eQAB0-0002rN-LU for emacs-orgmode@gnu.org; Sat, 16 Dec 2017 05:58:42 -0500 In-Reply-To: Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: "numbchild@gmail.com" , Org-mode , emacs-help This is a multi-part message in MIME format. --------------CEA8F5085777CF6F5394EE02 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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, numbchild@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]                 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/ --------------CEA8F5085777CF6F5394EE02 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

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, numbchild@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/

--------------CEA8F5085777CF6F5394EE02--