> I just tried to compile and test vim for the > first time in ages and got a segmentation fault. > > Environment: > > macos-10.14.6 > vim-8.2 patches 1-2251 > XQuartz 2.7.11 (xorg-server 1.18.4) > (plus other xorg stuff via macports might be relevant) > > Configure: > > ./configure \ > --disable-darwin \ > --with-x \ > --enable-gui=athena \ > --enable-multibyte \ > --with-mac-arch=current \ > --with-features=huge \ > --disable-acl > > Compiler: > > > gcc --version > Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr > --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1 > Apple clang version 11.0.0 (clang-1100.0.33.16) > Target: x86_64-apple-darwin18.7.0 > Thread model: posix > InstalledDir: > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
[...] > The first time, test_gui.vim crashed after a 32 second pause. > The second time, it crashed after 222 seconds. > > VIMRUNTIME=../../runtime ../vim -f -u unix.vim -u NONE -U NONE --noplugin > --not-a-term -S runtest.vim test_gui.vim > > > Vim: Caught deadly signal SEGV > Vim: Finished. That looks like a real crash. No idea why, but it's probably GUI related. > Found errors in Test_menu(): > Test caused Vim to exit: Test_menu() > SKIPPED Test_encoding_conversion(): gui_gtk feature missing > > The backtrace is: > > > lldb src/vim -c /cores/core.41972 > (lldb) target create "src/vim" --core "/cores/core.41972" > Core file '/cores/core.41972' (x86_64) was loaded. > (lldb) bt > warning: could not execute support code to read Objective-C class data in > the process. This may reduce the quality of type information available. > * thread #1, stop reason = signal SIGSTOP > * frame #0: 0x00007fff6aa8fbf6 libsystem_kernel.dylib`__kill + 10 > frame #1: 0x000000010229ff6b vim`mch_exit [inlined] may_core_dump at > os_unix.c:3432:2 [opt] > frame #2: 0x000000010229ff43 vim`mch_exit(r=0) at os_unix.c:3398 [opt] > frame #3: 0x00000001023fc838 vim`getout(exitval=0) at main.c:1689:5 > [opt] > frame #4: 0x00000001021facd4 vim`ex_quit_all(eap=0x0000000102944cf0) at > ex_docmd.c:5455:2 [opt] This is strange, it indicates that deadly_signal was set to SISTOP, but that does not appear in the signal table, because it can't be caught. Perhaps the definition of signals (mapping from name to number) isn't quite right? -- Be thankful to be in a traffic jam, because it means you own a car. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/202012311641.0BVGfnQ91265555%40masaka.moolenaar.net.
