Julien Lepiller <[email protected]> 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
