On Fri, Jun 07, 2019 at 09:46:21PM +0900, Osamu Aoki wrote: > 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...
https://wiki.debian.org/HowToGetABacktrace#Running_gdb gives some information on working with gdb. > Program received signal SIGSEGV, Segmentation fault. > 0x000055555574ae54 in multiqueue_new_child (parent=0x0) Hmm, a NULL pointer being passed in to multiqueue_new_child()... that's not correct. > ------------------------------------------ > 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... > > $ 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... It looks like you have systemd-coredump installed. If you reproduce the crash, then "coredumpctl -1 info" should provide the backtrace. For the detailed info, the wiki page's instructions would be better. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
