Bug#21803: marked as done (kdevelop generated programs crash on exit) by "F at lk Brettschneider" <gigafalk at yahoo.com>
owner at bugs.kde.org
Thu Aug 23 20:03:05 UTC 2001
Your message with subj: fixed in version 2.0
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
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.)
(administrator, KDE bugs database)
Received: (at submit) by bugs.kde.org; 7 Mar 2001 12:53:57 +0000
Received: (qmail 19040 invoked by uid 33); 7 Mar 2001 12:53:57 -0000
Date: 7 Mar 2001 12:53:57 -0000
Message-ID: <20010307125357.19039.qmail at master.kde.org>
To: submit at bugs.kde.org
Subject: kdevelop generated programs crash on exit
From: pflugshaupt at geobot.umnw.ethz.ch
Version: KDE 2.1.0
Installed from: SuSE
Compiler: gcc version 2.95.3 19991030 (prerelease/franzo/20000625)
OS: Linux 2.2.16 ppc
I can generate a program with KDevelop 1.4 and run it (the KDE 2 sample program, with no changes), but when I close or quit it, the KDE crash handler turns up and tells me the program received a signal 11 (SIGSEGV).
The backtrace gives the following:
0x6487e4 in ?? ()
#0 0x6487e4 in ?? ()
#1 0x0 in ?? ()
and claims to be unable to create a backtrace.
The same thing happens if I debug the program instead of running it.
Could this be a problem of my Linux setup? I've upgraded SuSE Linux PPC 7.0 with the new KDE 2.1 packages.
(Submitted via bugs.kde.org)
(Called from KBugReport dialog. Fields E-Mail manually changed)
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel