Hi, Please guide me ...
On Thu, Jun 06, 2019 at 08:33:05PM -0400, James McCoy wrote: > Control: tag -1 unreproducible moreinfo > > On Fri, Jun 07, 2019 at 12:41:48AM +0900, Osamu Aoki wrote: > > I just wanted to see how nvim behaves but ... > > > > $ nvim > > Segmentation fault (core dumped) > > $ nvim -u NONE > > Segmentation fault (core dumped) > > $ nvim -u NORC > > Segmentation fault (core dumped) > > Could you install neovim-dbgsym and post a backtrace? The buildds run > nvim (and its test suite), so this isn't a common issue. OK. Good to know. I tried with "root" and my newly added user "foo". It works ;-) No wonder normal test cases don't catch my problem. Even after renaming all home directory .vim/* .vimrc .vimino files and directories to other names, my normal user had problem... I got to starting nvim under GDB. $ gdb GNU gdb (Debian 8.2.1-2) 8.2.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) file /usr/lib/debug/.build-id/4d/1816cd8e71e23c455ca62765d0c2d48a703ef9.debug Reading symbols from /usr/lib/debug/.build-id/4d/1816cd8e71e23c455ca62765d0c2d48a703ef9.debug...done. (gdb) exec-file /usr/bin/nvim (gdb) run Starting program: /usr/bin/nvim Program received signal SIGSEGV, Segmentation fault. 0x000055555574ae54 in multiqueue_new_child (parent=0x0) at ../src/nvim/event/multiqueue.c:96 96 ../src/nvim/event/multiqueue.c: No such file or directory. After restarting GDB and placing break point here and run, I see: 0x000055555574ae23 <loop_schedule+83>: decl -0x73(%rax) 0x000055555574ae26 <loop_schedule+86>: mov $0x538,%ebx 0x000055555574ae2b <loop_schedule+91>: add $0x60,%rsp 0x000055555574ae2f <loop_schedule+95>: callq 0x5555555bc200 0x000055555574ae34 <loop_schedule+100>: add $0x8,%rsp 0x000055555574ae38 <loop_schedule+104>: mov %rbp,%rdi 0x000055555574ae3b <loop_schedule+107>: pop %rbx 0x000055555574ae3c <loop_schedule+108>: pop %rbp 0x000055555574ae3d <loop_schedule+109>: jmpq 0x5555555bd2c0 0x000055555574ae42: data16 nopw %cs:0x0(%rax,%rax,1) 0x000055555574ae4d: nopl (%rax) => 0x000055555574ae50 <multiqueue_new_child+0>: push %rbx 0x000055555574ae51 <multiqueue_new_child+1>: mov %rdi,%rbx 0x000055555574ae54 <multiqueue_new_child+4>: addq $0x1,0x28(%rdi) 0x000055555574ae59 <multiqueue_new_child+9>: mov $0x30,%edi Step from here causes (gdb) s Program received signal SIGSEGV, Segmentation fault. 0x000055555574ae54 in multiqueue_new_child (parent=0x0) at ../src/nvim/event/multiqueue.c:96 96 in ../src/nvim/event/multiqueue.c ------------------------------------------ The thing is I can't locate core file in my home directory like good old days nor in /tmp ... I thought I configured system for such . Can you tell me where to look for... $ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 62714 max locked memory (kbytes, -l) 65536 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 62714 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited $ cd /etc/systemd $ grep CORE user.conf #DefaultLimitCORE= DefaultLimitCORE=infinity $ cat /proc/sys/kernel/core_pattern |/lib/systemd/systemd-coredump %P %u %g %s %t 9223372036854775808 %h %e Hmmm... this is not /tmp/core ... ??? What does this mean... Anyway, if you know good tutorial for gdb use on recent Debian system, that may be what I need. Osamu
