[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs 25.1.1 coredumps if company-mode pops up in a magit commit buf

From: Filipe Silva
Subject: Re: Emacs 25.1.1 coredumps if company-mode pops up in a magit commit buffer window
Date: Thu, 9 Mar 2017 18:12:42 -0300

Hi Eli, 

I've further investigated the issue and found that this only happens if this minor mode: https://github.com/ninrod/vim-empty-lines-mode
is activated in conjunction with `with-editor-mode`. 

the vim-empty-lines-mode provides an emulation of the vim's empty lines indicator and uses an overlay. 

Yes I can try to do that. 


On Thu, Mar 9, 2017 at 1:14 PM, Eli Zaretskii <address@hidden> wrote:
> From: Filipe Silva <address@hidden>
> Date: Wed, 8 Mar 2017 18:06:40 -0300
> Hi. Everytime open a magit buffer to commit write a commit message and company mode pops up with a
> completion menu, emacs 25.1.1 core dumps on me.
> This is the line I used:
> gdb --batch --quiet -ex "thread apply all bt full" -ex "quit" /usr/local/bin/emacs core.2466 > coredump.txt
> My emacs version: GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.13) of 2017-02-22
> Here's the coredump.
> [...]
> Thread 1 (Thread 0x7f4036acda00 (LWP 2466)):
> #0 0x00007f403154b23b in raise () from /lib64/libpthread.so.0
> No symbol table info available.
> #1 0x00000000004e6361 in terminate_due_to_signal (address@hidden,
> backtrace_limit=backtrace_address@hidden) at emacs.c:381
> No locals.
> #2 0x00000000004fe503 in emacs_abort () at sysdep.c:2247
> No locals.
> #3 0x00000000004a55f5 in bidi_paragraph_init (dir=<optimized out>, address@hidden0x7ffd828deab0,
> no_default_p=no_default_p@entry=false) at bidi.c:1674
> bytepos = 266
> string_p = <optimized out>
> pstartbyte = <optimized out>
> begbyte = <optimized out>
> end = 266
> #4 0x000000000043fe4a in set_iterator_to_next (address@hidden,
> address@hidden) at xdisp.c:7426
> prev_scan_dir = 1
> #5 0x000000000043f4ce in forward_to_next_line_start (address@hidden,
> address@hidden0x7ffd828dc42f, bidi_it_prev=bidi_it_prev@entry=0x7ffd828dc430) at
> xdisp.c:6224
> old_selective = <optimized out>
> newline_found_p = false
> n = <optimized out>
> #6 0x000000000043f6aa in reseat_at_next_visible_line_start (address@hidden,
> >entry=false) at xdisp.c:6431

It's hard to understand how this happens: your build is an optimized
one, so many important values are not accessible to the debugger.  The
stuff that is shown seems to present a contradicting picture:
character position 266 is EOB, but it also has a newline character
there, which AFAIU cannot happen.

Can you prepare a recipe for reproducing this, from "emacs -Q",
loading all the necessary Lisp packages, and then showing the commands
you need to invoke to get Emacs to abort like this?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]