* Emacs sagmentation fault error on a big org-mode file movement
@ 2017-12-16 4:27 numbchild
2017-12-16 8:38 ` Eli Zaretskii
2017-12-16 10:58 ` Neil Jerram
0 siblings, 2 replies; 5+ messages in thread
From: numbchild @ 2017-12-16 4:27 UTC (permalink / raw)
To: Org-mode, emacs-help
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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Emacs sagmentation fault error on a big org-mode file movement
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
1 sibling, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2017-12-16 8:38 UTC (permalink / raw)
To: numbchild@gmail.com; +Cc: help-gnu-emacs, emacs-orgmode
> From: "numbchild@gmail.com" <numbchild@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 command
report-emacs-bug. If you can attach the file which causes the crash,
please do. Further discussion of this should be on the bug list, not
here (many Emacs developers don't read this list).
Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Emacs sagmentation fault error on a big org-mode file movement
2017-12-16 8:38 ` Eli Zaretskii
@ 2017-12-16 10:35 ` numbchild
0 siblings, 0 replies; 5+ messages in thread
From: numbchild @ 2017-12-16 10:35 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-help, Org-mode
That's very helpful . Thanks very much.
[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 4:38 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: "numbchild@gmail.com" <numbchild@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 command
> report-emacs-bug. If you can attach the file which causes the crash,
> please do. Further discussion of this should be on the bug list, not
> here (many Emacs developers don't read this list).
>
> Thanks.
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Emacs sagmentation fault error on a big org-mode file movement
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:58 ` Neil Jerram
2017-12-17 15:03 ` numbchild
1 sibling, 1 reply; 5+ messages in thread
From: Neil Jerram @ 2017-12-16 10:58 UTC (permalink / raw)
To: numbchild@gmail.com, Org-mode, emacs-help
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Emacs sagmentation fault error on a big org-mode file movement
2017-12-16 10:58 ` Neil Jerram
@ 2017-12-17 15:03 ` numbchild
0 siblings, 0 replies; 5+ messages in thread
From: numbchild @ 2017-12-17 15:03 UTC (permalink / raw)
To: Neil Jerram; +Cc: emacs-help, Org-mode
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/
>
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-12-17 15:03 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2017-12-17 15:03 ` numbchild
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).