From: Neil Jerram <neil@ossau.homelinux.net>
To: "numbchild@gmail.com" <numbchild@gmail.com>,
Org-mode <emacs-orgmode@gnu.org>,
emacs-help <help-gnu-emacs@gnu.org>
Subject: Re: Emacs sagmentation fault error on a big org-mode file movement
Date: Sat, 16 Dec 2017 10:58:36 +0000 [thread overview]
Message-ID: <00d6f98c-31b2-fd9e-e4af-e6d9445d8945@ossau.homelinux.net> (raw)
In-Reply-To: <CAL1eYu+BQvvq442mEc5cAPm3JGwetBx0wONmxzM0DgnHmO5MQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
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/
[-- Attachment #2: Type: text/html, Size: 4660 bytes --]
next prev parent reply other threads:[~2017-12-16 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 4:27 Emacs sagmentation fault error on a big org-mode file movement numbchild
2017-12-16 8:38 ` Eli Zaretskii
2017-12-16 10:35 ` numbchild
2017-12-16 10:58 ` Neil Jerram [this message]
2017-12-17 15:03 ` numbchild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00d6f98c-31b2-fd9e-e4af-e6d9445d8945@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--cc=emacs-orgmode@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=numbchild@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).