Bug#625937: kdevelop: crash when opening source file
Package: kdevelop
Version: 4:4.0.1-1
Severity: grave
Justification: renders package unusable
kdevelop crashes when i try to open a .c file, but it is fine with .txt files
and so on.
That problem makes it useless...
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38.3-penelope (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kdevelop depends on:
ii kdebase-runtime 4:4.6.2-1 runtime components from the offici
ii kdevelop-data 4:4.0.1-1 data files for the KDevelop IDE
ii kdevplatform1-libs 1.0.1-1 shared libraries for the KDevelop
ii lcov 1.9-2 Summarise Code coverage informatio
ii libc6 2.13-2 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.6.0-6 GCC support library
ii libkdecore5 4:4.6.2-1 KDE Platform Core Library
ii libkdeui5 4:4.6.2-1 KDE Platform User Interface Librar
ii libkio5 4:4.6.2-1 Network-enabled File Management Li
ii libkparts4 4:4.6.2-1 Framework for the KDE Platform Gra
ii libktexteditor4 4:4.6.2-1 KTextEditor interfaces for the KDE
ii libprocessui4a 4:4.6.2-2 library for ksysguard process user
ii libqt4-dbus 4:4.7.2-4 Qt 4 D-Bus module
ii libqt4-help 4:4.7.2-4 Qt 4 help module
ii libqt4-network 4:4.7.2-4 Qt 4 network module
ii libqt4-script 4:4.7.2-4 Qt 4 script module
ii libqt4-webkit 4:4.7.2-4 transitional package for Qt 4 WebK
ii libqtcore4 4:4.7.2-4 Qt 4 core module
ii libqtgui4 4:4.7.2-4 Qt 4 GUI module
ii libstdc++6 4.6.0-6 The GNU Standard C++ Library v3
ii libsublime1 1.0.1-1 an user interface library
ii libthreadweaver4 4:4.6.2-1 ThreadWeaver Library for the KDE P
Versions of packages kdevelop recommends:
ii gdb 7.2-1 The GNU Debugger
ii valgrind 1:3.6.0~svn11254+nmu1 A memory debugger and profiler
Versions of packages kdevelop suggests:
pn cmake <none> (no description available)
pn kdevelop-l10n <none> (no description available)
-- no debconf information
Reply to: