Bug 163516 - kdevelop crashed while editing some c++ source
Summary: kdevelop crashed while editing some c++ source
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-08 11:56 UTC by Cristi
Modified: 2008-06-08 13:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cristi 2008-06-08 11:56:40 UTC
Version:           3.9.0 (using 4.00.81 (KDE 4.0.81 >= 20080527), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.25-gentoo-r4

I was learning c++ and writting a simple c++ file when this happened. This is the backtrace:
Application: KDevelop (kdevelop), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0x7f709a354700 (LWP 11339)]
[New Thread 0x44485950 (LWP 12640)]
[New Thread 0x43c84950 (LWP 12639)]
[New Thread 0x43483950 (LWP 12638)]
[New Thread 0x42c82950 (LWP 11347)]
[New Thread 0x42481950 (LWP 11346)]
[New Thread 0x41728950 (LWP 11341)]
[New Thread 0x40ab8950 (LWP 11340)]
[KCrash handler]
#5  KDevelop::DocumentRangeObject::d_func (this=0x0)
    at /var/tmp/paludis/kde-base-kdevplatform-scm/work/kdevplatform-scm/editor/documentrangeobject.h:101
#6  0x00007f7091e163ec in KDevelop::DocumentRangeObject::range (this=0x0)
    at /var/tmp/paludis/kde-base-kdevplatform-scm/work/kdevplatform-scm/editor/documentrangeobject.cpp:185
#7  0x00007f7088d6b80a in CodeCompletionWorker::computeCompletions (
    this=0x1a2eb80, context=@0x7fffa2397830, position=@0x98131e0,
    view=<value optimized out>)
    at /var/tmp/paludis/dev-util-kdevelop-scm/work/kdevelop-scm/languages/cpp/cppcodecompletionworker.cpp:79
#8  0x00007f7088d6bc4d in CodeCompletionWorker::qt_metacall (this=0x1a2eb80,
    _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x98a9800)
    at /var/tmp/paludis/dev-util-kdevelop-scm/work/kdevelop_build/languages/cpp/cppcodecompletionworker.moc:73
#9  0x00007f7099e9e577 in QObject::event (this=0x1a2eb80, e=0x9875f70)
    at kernel/qobject.cpp:1131
#10 0x00007f70937043af in QApplicationPrivate::notify_helper (this=0x15814d0,
    receiver=0x1a2eb80, e=0x9875f70) at kernel/qapplication.cpp:3772
#11 0x00007f7093708355 in QApplication::notify (this=0x7fffa2398270,
    receiver=0x1a2eb80, e=0x9875f70) at kernel/qapplication.cpp:3739
#12 0x00007f70982ed9fe in KApplication::notify (this=0x7fffa2398270,
    receiver=0x1a2eb80, event=0x9875f70)
    at /var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kdeui/kernel/kapplication.cpp:311
#13 0x00007f7099e8e168 in QCoreApplication::notifyInternal (
    this=0x7fffa2398270, receiver=0x1a2eb80, event=0x9875f70)
    at kernel/qcoreapplication.cpp:587
#14 0x00007f7099e8f3bd in QCoreApplicationPrivate::sendPostedEvents (
    receiver=0x0, event_type=0, data=0x156b380)
    at kernel/qcoreapplication.h:215
#15 0x00007f709379241d in QEventDispatcherX11::processEvents (this=0x1581440,
    flags=@0x7fffa2398100)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#16 0x00007f7099e8d565 in QEventLoop::processEvents (
    this=<value optimized out>, flags=@0x7fffa2398140)
    at kernel/qeventloop.cpp:149
#17 0x00007f7099e8d6be in QEventLoop::exec (this=0x7fffa2398180,
    flags=@0x7fffa2398190) at kernel/qeventloop.cpp:200
#18 0x00007f7099e8f709 in QCoreApplication::exec ()
    at kernel/qcoreapplication.cpp:845
#19 0x0000000000406c1a in main (argc=1, argv=0x7fffa2399208)
    at /var/tmp/paludis/dev-util-kdevelop-scm/work/kdevelop-scm/src/main.cpp:209
#0  0x00007f7092b2cc21 in nanosleep () from /lib64/libc.so.6
Comment 1 Cristi 2008-06-08 12:24:34 UTC
wait...got it:
so editing a c++ file and writting :
#include <string>
#include <fstream>
using namespace std;
int main (){
ifs            <===that is where it crashes
Comment 2 Andreas Pakulat 2008-06-08 13:46:02 UTC
sorry but bugreports against kdevelop4 are useless because the code-base changes almost on a daily bases. If you get crashes and can reproduce them please send a mail to kdevelop-devel@kdevelop.org.