FS#29549 - [gvim] crash on mouse interaction

Attached to Project: Arch Linux
Opened by H.pferd (stosch) - Saturday, 21 April 2012, 10:27 GMT
Last edited by Thomas Dziedzic (tomd123) - Sunday, 29 April 2012, 18:58 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Dziedzic (tomd123)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
With the upgrade from gvim and vim-runtime 7.3.495-1 to 7.3.495-2 gvim (not vim!) crashes whenever I do anything with my mouse (scrolling, clicking etc) in it.
Downgrading solves the problem for me. It is not related to any file extension (https://bugs.archlinux.org/task/29377).



Error message:
Vim: Caught deadly signal ILL
Vim: Finished.
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Sunday, 29 April 2012, 18:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  pkgrel 3
Comment by Jelle van der Waa (jelly) - Sunday, 22 April 2012, 09:32 GMT
Works for me here. Custom vimrc?
Comment by Thomas Dziedzic (tomd123) - Sunday, 22 April 2012, 13:50 GMT
Start gvim with "gvim -u NONE" and see if it happens.

I can't reproduce this, you will need to provide me with more info for this to possibly get solved.
https://wiki.archlinux.org/index.php/Step_By_Step_Debugging_Guide
Comment by H.pferd (stosch) - Monday, 23 April 2012, 18:04 GMT
Thank you for the responses.

I get the same behaviour with deactivated custom vimrc.
GDB gives no information.
I recompiled with CFLAG "-g -O0 -fbuiltin" and again got the same..
Strace gives the following: http://pastebin.com/afizV2mu
But sadly I cannot get any useful information from this.
The problem does not appear on my laptops which are a little newer than this old AthlonXP - could this be a reason?

If you need further information let me know.
Comment by Thomas Dziedzic (tomd123) - Tuesday, 24 April 2012, 15:04 GMT
Can you post a useful backtrace from gdb?
Comment by H.pferd (stosch) - Tuesday, 24 April 2012, 15:51 GMT
I haven't done this before, but according to the link you sent me I should do something like "gdb gvim" etc, right?
When I enter "bt full" I receive "No stack.". There is also no core-file. Did I miss something?
By the way: My system is fully up to date.
Comment by Thomas Dziedzic (tomd123) - Tuesday, 24 April 2012, 16:35 GMT
Run: gdb gvim
At the gdb prompt type run
Then get the backtrace.

You will need to compile gvim w/ debug symbols.
Comment by H.pferd (stosch) - Wednesday, 25 April 2012, 14:16 GMT
Yes, that is exactly what I was doing. Compiled with "-g" option nevertheless received "No stack.". That means that the application is not segfaulting, I think!? Sorry, that I cannot give you any useful information so far.
Comment by Szunti (Szunti) - Thursday, 26 April 2012, 18:01 GMT
I have the same problem on my 32 bit system, but not on the 64 bit one. I guess this is because the

export CFLAGS="-march=x86-64 ...

added in the last version in the PKGBUILD. I changed it to -march=native on my 32 bit system, and the problem vanished.
Comment by H.pferd (stosch) - Sunday, 29 April 2012, 15:37 GMT
Sorry for the long pause, I haven't been at home over the past days.

@Szunti:
Thank you for your tip. I tried it and it solved the problem for me.

But still it is strange, that the problem does not appear on my i686 laptop. Does this mean it is related to some processor flags?
Comment by Thomas Dziedzic (tomd123) - Sunday, 29 April 2012, 16:34 GMT
Just pushed vim pkgrel 3, can you confirm that it doesn't crash for you?
Comment by Szunti (Szunti) - Sunday, 29 April 2012, 18:46 GMT
No crash for clicking or scrolling anymore here.

Loading...