Bug#40868: marked as done (crash when opening new project with existing project) by Stephan Binner <binner at kde.org>

Stephan Kulow owner at bugs.kde.org
Sat Apr 13 21:08:47 UTC 2002


Your message with subj: crash when opening new project with existing project

Thank you for your bug report.
The bug that you reported appears to be a packaging bug, due to a problem
in the way in which your distribution/vendor has packaged KDE for
distribution. The bug report will be closed since it is not a KDE problem=
=2E
Please send the bug report to your distribution/vendor instead.


has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 13 Apr 2002 01:40:46 +0000
Received: (qmail 26322 invoked by uid 33); 13 Apr 2002 01:40:46 -0000
Date: 13 Apr 2002 01:40:46 -0000
Message-ID: <20020413014046.26321.qmail at mail.kde.org>
To: submit at bugs.kde.org
Subject: crash when opening new project with existing project
From: crazycrusoe at yahoo.com
X-KDE-Received: -202.180.83.6

Package:           kdevelop
Version:           2.1 (using KDE 3.0.0 )
Severity:          normal
Installed from:    Mandrake Linux 8.2 i586 - Cooker
Compiler:          gcc version 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)
OS:                Linux (i686) release 2.4.18-6mdk
OS/Compiler notes: 

looking arnd in kdevelop 2.1, which i got along with kde 3 from pclinuxonline.com rpms for mandrake made by textar.
i had a project open and tried opening a custom project from the wizard, created and clicked exit and kdevelop crashed, below is the backtrace, i hope it helps

============================
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 2337)]
0x414cc409 in wait4 () from /lib/libc.so.6
#0  0x414cc409 in wait4 () from /lib/libc.so.6
#1  0x4154b98c in __check_rhosts_file () from /lib/libc.so.6
#2  0x413e8d56 in waitpid (pid=6489, stat_loc=0x0, options=0)
    at wrapsyscall.c:172
#3  0x40aff89e in KCrash::defaultCrashHandler ()
   from /opt/kde3//lib/libkdecore.so.4
#4  0x40c3ca47 in _IO_2_1_stderr_ () from /usr/lib/libstdc++-libc6.2-2.so.3


(Submitted via bugs.kde.org)
(Called from KBugReport dialog)





More information about the KDevelop-devel mailing list