[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 162887] New: Crash when loading a project on start
From:       Amroth <e9.amroth () gmail ! com>
Date:       2008-05-30 12:36:19
Message-ID: 20080530143618.162887.e9.amroth () gmail ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=162887         
           Summary: Crash when loading a project on start
           Product: kdevelop
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: e9.amroth gmail com


Version:           SVN trunk (KDE4) (using Devel)
Installed from:    Compiled sources
Compiler:          gcc (SUSE Linux) 4.3.1 20080507 (prerelease) [gcc-4_3-branch \
                revision 135036]  Installed from package on Novell OpenSUSE 11.0 beta \
                3.
OS:                Linux

I'm on OpenSUSE 11.0 beta3, with all latest updates. My Qt4.4 comes from the distro's \
repositories, and my KDE4 is built from sources updated yesterday, april 29 ( Version \
4.00.81 (KDE 4.0.81 >= 20080527) ).

When I open KDevelop4, it loads flawlessly. I then open a project, and check the \
general option to reopen projects on exit, and the background parser, then accept and \
close the program. At the next start, KDevelop will crash randomly within one or two \
minutes. The console output shows that it's trying to parse the whole /usr/include \
directory (which I think it shouldn't, or at least not if I don't want it to); but it \
randomly crashes while performing this operation. Opening KDev, quickly disabling the \
background parser, and applying the change, allows KDev to not crash at next start.

I'm attaching two GDB console logs + backtraces.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs


[prev in list] [next in list] [prev in thread] [next in thread]