From mboxrd@z Thu Jan  1 00:00:00 1970
From: "numbchild@gmail.com" <numbchild@gmail.com>
Subject: Re: Emacs sagmentation fault error on a big org-mode file movement
Date: Sun, 17 Dec 2017 23:03:54 +0800
Message-ID: <CAL1eYuKKmn-spGEFLpZSSF=1muekc91dX=Hnes6vvSm=hE_XJQ@mail.gmail.com>
References: <CAL1eYu+BQvvq442mEc5cAPm3JGwetBx0wONmxzM0DgnHmO5MQw@mail.gmail.com>
	<00d6f98c-31b2-fd9e-e4af-e6d9445d8945@ossau.homelinux.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Return-path: <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org>
In-Reply-To: <00d6f98c-31b2-fd9e-e4af-e6d9445d8945@ossau.homelinux.net>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-gnu-emacs>,
	<mailto:help-gnu-emacs-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-gnu-emacs/>
List-Post: <mailto:help-gnu-emacs@gnu.org>
List-Help: <mailto:help-gnu-emacs-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-gnu-emacs>,
	<mailto:help-gnu-emacs-request@gnu.org?subject=subscribe>
Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org
Sender: "help-gnu-emacs"
	<help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org>
To: Neil Jerram <neil@ossau.homelinux.net>
Cc: emacs-help <help-gnu-emacs@gnu.org>, Org-mode <emacs-orgmode@gnu.org>
List-Id: emacs-orgmode.gnu.org

I'm doing it try to reproduce this sagment fault. but can't reproduce it
for now.

[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/

On Sat, Dec 16, 2017 at 6:58 PM, Neil Jerram <neil@ossau.homelinux.net>
wrote:

> 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/
>
>
>