Re: gvim segfaulting on Solaris 10
Bram Moolenaar a écrit : Smells like a problem in the GUI libraries. Or it could be a compiler optimizer bug again, try compiling without -O2. But I guess it's the libraries. Yes, you were right. After I found out that the very same binary worked on my Solaris Express install (the -dev branch of Solaris), I had a harder look at the most recently installed patches. There was one for fontconfig, and the last functions called were for fontconfig, the evidence was overwhelming, it was the culprit. Once I had it backed out, the binary worked. FWIW, tt's that one, out 3 days ago: 123495-02 X11 6.6.2_x86: fontconfig patch I'm back to -01, which works. Does it always print those two lines when gvim starts? I don't know what this accessibility stuff does, but it might be worth looking into whether it is related to the crash. Yes, it's a JDS thing, it's also displayed for other GNOME apps on Solaris. Is /usr/sfw a standard place for something? Then perhaps configure should be adjusted to check it. On Solaris 10, it's where freetype and Xrender live, so it's needed at build time, IIRC, because else, some dependencies won't link correctly. Actually, I did that a while ago, and didn't try again since them, so maybe it's not needed anymore (the .pc files should provide the correct paths). If you want, I'll build again to confirm that. I don't see a Vim function in the stack trace. It might be something in Pango. I've seen pango crash before. You would have to dig into this to find out if we can work around it. Definitely not a vim issue, sorry for bothering you, I'll be sure to open a case with Sun about that on Monday. Thanks for your answer! Laurent
Re: gvim segfaulting on Solaris 10
Ali Akcaagac a écrit : For what reasons does gVIM require Bonobo on Solaris ? It's not gvim asking for it, but the JDS/GNOME libs (modified by Sun for the accessibility stuff). Laurent
Re: gvim segfaulting on Solaris 10
Bram Moolenaar wrote: Is /usr/sfw a standard place for something? Then perhaps configure should be adjusted to check it. Checked that. No need anymore for it. Ir probably dated from my first builds on the Solaris 10 beta, 2 years ago. Laurent
gvim segfaulting on Solaris 10
Hi all, I built vim 7.0.110 on Solaris 10 U1 x86, fully patched, using Sun Studio 11 or Solaris' GCC 3.4.3. Building went fine, however, test 16 failed (no output). What happens is that gvim fails on startup with a segfault: $ gvim GTK Accessibility Module initialized Bonobo accessibility support initialized Vim: Caught deadly signal SEGV Vim: Finished. Segmentation Fault (core dumped) Just running vim works: $ vim ~ VIM - Vi IMproved ~ ~ version 7.0.110 I built it using a very simple configuration: export PATH=/usr/bin:/usr/ccs/bin:/opt/SUNWspro/bin LDFLAGS='-L/usr/sfw/lib -R/usr/sfw/lib' \ ./configure --prefix=/opt/vim-7.0.110 \ --enable-multibyte And here's the pstack of the core if it can be useful: $ pstack core.vim.14541 core 'core.vim.14541' of 14541: gvim fd1b0557 kill (82ba9cc, 815c0b0, 1, 82bd2e8, 0, 0) + 7 081c183a mch_exit (1) + 8a 0815c0b0 getout (1) + 210 08185884 preserve_exit (8, 82ba9fc, fd1afd8f, b, 0, 82baa8c) + c4 081bfa19 (b, 0, 82baa8c) fd1afd8f __sighndlr (b, 0, 82baa8c, 81bf880) + f fd1a6355 call_user_handler (b, 0, 82baa8c) + 22b fd1a64d5 sigacthandler (b, 0, 82baa8c) + bb --- called from signal handler with signal 11 (SIGSEGV) --- fcfdf908 FcHideFont (83ff0e8, 8429280, 8429268, 80468e0) + d8 fcfe0979 FcFontSetSort (83f8be0, 804695c, 1, 83f5d58, 1, 0) + 1c9 fcfe0d1a FcFontSort (83f8be0, 83f5d58, 1, 0, 80469a8, 83f5d58) + ca fd6e8043 pango_fc_font_map_get_patterns () + 157 Any idea what's going wrong? Would it be a vim or a Solaris GNOME issue? Thanks in advance for any hint! Laurent
