Bug#428176: vim-full: chrashes with SIGABRT when trying to select text with V
reassign 428176 libxt6 1:1.0.5-3 retitle 428176 libxt6: GetConversion() calls XtFree() on a NULL pointer thanks On Sat, Jun 16, 2007 at 06:11:40PM +0100, James Vega wrote: On Sat, Jun 09, 2007 at 06:06:50PM +0200, Sune Vuorela wrote: Program received signal SIGABRT, Aborted. [Switching to Thread -1229543216 (LWP 18110)] 0xb7f417f2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) bt #0 0xb7f417f2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0xb70e1d60 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb70e35b1 in abort () from /lib/i686/cmov/libc.so.6 #3 0xb711808b in __libc_message () from /lib/i686/cmov/libc.so.6 #4 0xb711feed in _int_free () from /lib/i686/cmov/libc.so.6 #5 0xb7123530 in free () from /lib/i686/cmov/libc.so.6 #6 0xb7628d31 in XtFree (ptr=0x0) at ../../src/Alloc.c:170 #7 0xb764cf4b in GetConversion (ctx=0x82d72c8, event=0xbfd1f5c4, target=425, property=291, widget=0x82f6778) at ../../src/Selection.c:774 For some reason, GetConversion appears to be calling XtFree on a NULL pointer. This is probably related to the messages we saw about using a locale (noted below) that libx11 doesn't support. I'll take a look at libx11 and probably reassign it to them. #8 0xb764d0db in HandleSelectionEvents (widget=0x82f6778, closure=0x82d72c8, event=0xbfd1f5c4, cont=0xbfd1f46b \001\\\207f·) at ../../src/Selection.c:854 #9 0xb76370f4 in XtDispatchEventToWidget (widget=0x82f6778, event=0xbfd1f5c4) at ../../src/Event.c:874 #10 0xb7637aaf in _XtDefaultDispatcher (event=0xbfd1f5c4) at ../../src/Event.c:1335 #11 0xb7636a67 in XtDispatchEvent (event=0xbfd1f5c4) at ../../src/Event.c:141 [snip useless backtrace with no symbols] -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-vserver-k7 (SMP w/1 CPU core) Locale: LANG=en_DK.ISO-8859-15, LC_CTYPE=en_DK.ISO-8859-15 (charmap=ISO-8859-15) Reassigning to libxt6. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#428176: vim-full: chrashes with SIGABRT when trying to select text with V
On Sat, Jun 09, 2007 at 06:06:50PM +0200, Sune Vuorela wrote: Program received signal SIGABRT, Aborted. [Switching to Thread -1229543216 (LWP 18110)] 0xb7f417f2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) bt #0 0xb7f417f2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0xb70e1d60 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb70e35b1 in abort () from /lib/i686/cmov/libc.so.6 #3 0xb711808b in __libc_message () from /lib/i686/cmov/libc.so.6 #4 0xb711feed in _int_free () from /lib/i686/cmov/libc.so.6 #5 0xb7123530 in free () from /lib/i686/cmov/libc.so.6 #6 0xb7628d31 in XtFree (ptr=0x0) at ../../src/Alloc.c:170 #7 0xb764cf4b in GetConversion (ctx=0x82d72c8, event=0xbfd1f5c4, target=425, property=291, widget=0x82f6778) at ../../src/Selection.c:774 For some reason, GetConversion appears to be calling XtFree on a NULL pointer. This is probably related to the messages we saw about using a locale (noted below) that libx11 doesn't support. I'll take a look at libx11 and probably reassign it to them. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-vserver-k7 (SMP w/1 CPU core) Locale: LANG=en_DK.ISO-8859-15, LC_CTYPE=en_DK.ISO-8859-15 (charmap=ISO-8859-15) James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#428176: vim-full: chrashes with SIGABRT when trying to select text with V
On 6/11/07, Sune Vuorela [EMAIL PROTECTED] wrote: On Monday 11 June 2007, James Vega wrote: if you can ship me a way to do a debug build, I would like to try reproduce it. Hopefully my response to your other bug will help you produce a debug build. I'll also try and get some time to build a debug version in case you are unable to. I finally got it build (using unclean environment and fakeroot debian/rules binary). Were you using sudo to build before? sudo automatically cleans the environment variables so you have to specifically tell it to keep the relevant DEB* variables. See the env_keep option in sudoers(5). Now I got debugging symbols. But vim won't crash. :/ If I reinstall the version from the mirrors, vim crashes again. but with a backtrace as useless as before. I don't know how to proceed from here. Bugs where the debugger/debugging symbols 'fix' things are annoying. I'll be around for DebConf so maybe we can look into it then. Ideally I'd be able to reproduce it but so far that isn't happening. James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428176: vim-full: chrashes with SIGABRT when trying to select text with V
On 6/9/07, Sune Vuorela [EMAIL PROTECTED] wrote: If I try to select any text in my vim, I just get it failing with SIGABRT. Does this happen only with a specific file? If so, would you be able to attach the file that is causing it? Does it happen no matter what text you try to visually select or does it depend on the text/area that is visually selected? if you can ship me a way to do a debug build, I would like to try reproduce it. Hopefully my response to your other bug will help you produce a debug build. I'll also try and get some time to build a debug version in case you are unable to. James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428176: vim-full: chrashes with SIGABRT when trying to select text with V
On Monday 11 June 2007, James Vega wrote: On 6/9/07, Sune Vuorela [EMAIL PROTECTED] wrote: If I try to select any text in my vim, I just get it failing with SIGABRT. Does this happen only with a specific file? If so, would you be able to attach the file that is causing it? Does it happen no matter what text you try to visually select or does it depend on the text/area that is visually selected? It happens every time. on new files where I enter some text, in existing files where I edit stuff first, in existing files where 'V' is the first thing I want to do - so - every time. It happens when I run as user, when I do sudo vim, well.. every time. if you can ship me a way to do a debug build, I would like to try reproduce it. Hopefully my response to your other bug will help you produce a debug build. I'll also try and get some time to build a debug version in case you are unable to. thanks. ALternatively, if you are around debconf, I am available from friday afternoon. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428176: vim-full: chrashes with SIGABRT when trying to select text with V
On Monday 11 June 2007, James Vega wrote: if you can ship me a way to do a debug build, I would like to try reproduce it. Hopefully my response to your other bug will help you produce a debug build. I'll also try and get some time to build a debug version in case you are unable to. I finally got it build (using unclean environment and fakeroot debian/rules binary). Now I got debugging symbols. But vim won't crash. :/ If I reinstall the version from the mirrors, vim crashes again. but with a backtrace as useless as before. I don't know how to proceed from here. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
