From: Ricardo Wurmus <rekado@elephly.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 34616@debbugs.gnu.org
Subject: bug#34616: neovim segfaults
Date: Fri, 22 Feb 2019 18:11:52 +0100 [thread overview]
Message-ID: <87r2bz3fzb.fsf@elephly.net> (raw)
In-Reply-To: <767bed0d2f47c74490a878b801dc715d@lepiller.eu>
Julien Lepiller <julien@lepiller.eu> writes:
> I think that's what you mean:
>
> Thread 2 "nvim" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ffff6206700 (LWP 28664)]
> 0x00007ffff79682ad in __strcmp_avx2 () from
> /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/libc.so.6
> (gdb) bt
> #0 0x00007ffff79682ad in __strcmp_avx2 () from
avx2…? Is this indicative of libtermkey being tuned to a certain
CPU type?
> /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/libc.so.6
> #1 0x0000000000505b31 in strequal ()
> #2 0x000000000045681e in tui_tk_ti_getstr ()
> #3 0x00007ffff7e649a5 in try_load_terminfo_key () from
> /gnu/store/pl7nh8chyp0av6lb7qck5n9mvvaz24z5-libtermkey-0.21.1/lib/libtermkey.so.1
> #4 0x00007ffff7e64b59 in load_terminfo () from
> /gnu/store/pl7nh8chyp0av6lb7qck5n9mvvaz24z5-libtermkey-0.21.1/lib/libtermkey.so.1
> #5 0x00007ffff7e64eda in start_driver () from
> /gnu/store/pl7nh8chyp0av6lb7qck5n9mvvaz24z5-libtermkey-0.21.1/lib/libtermkey.so.1
> #6 0x00007ffff7e6007e in termkey_start () from
> /gnu/store/pl7nh8chyp0av6lb7qck5n9mvvaz24z5-libtermkey-0.21.1/lib/libtermkey.so.1
So the problem is in libtermkey. Can we reproduce this with another
package using libtermkey?
--
Ricardo
next prev parent reply other threads:[~2019-02-22 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 13:06 bug#34616: neovim segfaults Julien Lepiller
2019-02-22 15:06 ` Ricardo Wurmus
2019-02-22 15:13 ` Julien Lepiller
2019-02-22 15:57 ` Ricardo Wurmus
2019-02-22 16:35 ` Julien Lepiller
2019-02-22 17:11 ` Ricardo Wurmus [this message]
2019-02-24 9:02 ` Efraim Flashner
2019-03-01 16:31 ` Ricardo Wurmus
2019-03-05 19:53 ` Bradley Haggerty
[not found] <CAE4v=pg1YHwn4_xqJCpARYyn2qY1qK=o_aX6zB2fsGLN6je53A@mail.gmail.com>
2019-03-07 10:25 ` Gábor Boskovits
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2bz3fzb.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=34616@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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/guix.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).