kdevelop crashed with SIGSEGV in KDirWatch::contains()

Bug #468235 reported by Rogozin Oleg
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDevelop
Fix Released
High
kdevelop (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: kdevelop

I was browsing projects files with tool "Projects", when crash emerged

ProblemType: Crash
Architecture: amd64
Date: Sun Nov 1 13:06:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdevelop
Package: kdevelop 4:3.9.95-0ubuntu3
ProcCmdline: /usr/bin/kdevelop
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7fe35253d3de: mov 0x30(%r13),%rax
 PC (0x7fe35253d3de) ok
 source "0x30(%r13)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdevelop
StacktraceTop:
 ?? () from /usr/lib/libkio.so.5
 KDirWatch::contains(QString const&) const ()
 ?? () from /usr/lib/kde4/kdevcmakemanager.so
 ?? () from /usr/lib/kde4/kdevcmakemanager.so
 QMetaObject::activate(QObject*, int, int, void**) ()
Title: kdevelop crashed with SIGSEGV in KDirWatch::contains()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1891): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (operapluginwrapper-ia32-linux:4304): Gdk-WARNING **: XID collision, trouble ahead

Revision history for this message
Rogozin Oleg (olegrog) wrote :
Rogozin Oleg (olegrog)
description: updated
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:KDirWatchPrivate::entry (this=0x0, _path=@0x7fffda9e1d70)
KDirWatch::contains (this=0x174d660,
CMakeManager::dirtyFile (this=0x20719c0,
CMakeManager::qt_metacall (this=0x20719c0,
QMetaObject::activate ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdevelop (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in kdevelop (Ubuntu):
importance: Medium → Low
status: New → Triaged
Changed in kdevelop4:
status: Unknown → New
visibility: private → public
Changed in kdevelop4:
status: New → Fix Released
Changed in kdevelop4:
importance: Unknown → High
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.