vim.gtk crashed with SIGSEGV in free()

Bug #777023 reported by vlad
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: vim-gtk

vim got SEGV

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: vim-gtk 2:7.2.330-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed May 4 13:58:47 2011
ExecutablePath: /usr/bin/vim.gtk
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: vi
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=ru_UA.utf8
SegvAnalysis:
 Segfault happened at: 0x95d416 <__kernel_vsyscall+2>: ret
 PC (0x0095d416) ok
 destination "(%esp)" (0xbfb845a8) ok
 SP (0xbfb845a8) ok
 Reason could not be automatically determined. (Unhandled exception in kernel code?)
Signal: 11
SourcePackage: vim
StacktraceTop:
 free () from /lib/libc.so.6
 XtFree () from /usr/lib/libXt.so.6
 ?? () from /usr/lib/libXt.so.6
 ?? () from /usr/lib/libXt.so.6
 XtDispatchEventToWidget () from /usr/lib/libXt.so.6
Title: vim.gtk crashed with SIGSEGV in free()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
vlad (devvlad) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 *__GI___libc_free (mem=0xbfb84b88) at malloc.c:3724
 XtFree (ptr=0xbfb00000 <Address 0xbfb00000 out of bounds>)
 GetConversion (ctx=0x8e102a8, event=0xbfb84fec, target=437,
 HandleSelectionEvents (widget=0x8ddfe08, closure=0x8e102a8,
 XtDispatchEventToWidget (widget=0x8ddfe08, event=0xbfb84fec)

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in vim (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in vim (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.