FS#43406 - [gvim] Stopped working upon recent update -- libXt

Attached to Project: Arch Linux
Opened by stephen (hwkiller) - Sunday, 11 January 2015, 05:49 GMT
Last edited by Anatol Pomozov (anatolik) - Friday, 25 March 2016, 03:11 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I am using the gvim package.
I updated recently and vim stopped working.

The error is:
Vim: Caught deadly signal BUS
Vim: Finished.
zsh: bus error vim

vim -X works.
gvim works.

I attached the valgrind output for both vim and vim -X, and gdb output from vim (gdb.noX) and vim -X (gdb.X).
That is, *.X means I used the -X option, confusingly meaning that X isn't connected to.

Additional info:
Version : 7.4.560-1


Steps to reproduce:
Run vim, watch it fail.
Run gvim or vim -X, and it will succeed.
   gdb.noX (0.3 KiB)
   gdb.X (0.9 KiB)
   valgrind.noX (60.9 KiB)
   valgrind.X (44 KiB)
   pacman.log (22.8 KiB)
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Friday, 25 March 2016, 03:11 GMT
Reason for closing:  No response
Comment by Anatol Pomozov (anatolik) - Monday, 12 January 2015, 04:14 GMT
Hmm, I can't reproduce the crash... SIGBUS in XtCvtStringToPixel() it is even more weird.. And I can't google any similar crashes.

Try to recompile the vim package with (debug !strip) PKGBUILD options to get more useful gdb stack trace. And report the issue upstream.
Comment by stephen (hwkiller) - Monday, 12 January 2015, 05:58 GMT
Hey Anatol,
Thanks for the reply.
Should I report this to vim or xorg upstream?
Comment by Anatol Pomozov (anatolik) - Monday, 12 January 2015, 06:45 GMT
Start with vim maillist.

Also provide repro steps for the issue. I do not see any problem with my vim/gvim. If none can reproduce this issue then it might be some problem with your local environment.

What CPU do you have? Do you use 64bit packages?
Comment by stephen (hwkiller) - Monday, 12 January 2015, 07:20 GMT
The repro steps were pretty much as-is. I upgraded. I ran vim in terminal. It spits out the BUS error. Nothing more to it.

model name : Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz

Yes, 64bit packages.
Comment by Anatol Pomozov (anatolik) - Monday, 12 January 2015, 07:49 GMT
Looking at your pacman.log I see that you built vim locally (did you use ABS files?). Does it make any difference if you install official binary package from server?
Comment by stephen (hwkiller) - Thursday, 15 January 2015, 03:37 GMT
Hey Anatol, I wanted to respond and update you on the situation:

1) I discovered the bug using the official arch binary. I repackaged it with the debugging symbols so that I could run it through gdb.

2) I emailed the vim bug person (Bram) about the problem. He requested that I try using 'where' in gdb to find where the program is halting. So again, I had to then recompile libXt with debugging symbols to see that. Merely recompiling libXt fixed the issue. This should be reassigned to the maintainer of libXt. Arch may need a rebuild of it for some reason.

TLDR: It's libXt's fault; the arch maintainer needs to rebuild it.
Comment by Anatol Pomozov (anatolik) - Saturday, 19 March 2016, 18:28 GMT
Is it fixed?

Loading...