Bug#27769: marked as done (kdevelop crashed when using menu to goto next, previous error line number) by John Firebaugh <jfirebaugh at kde.org>

Stephan Kulow owner at bugs.kde.org
Fri Jul 27 03:18:03 UTC 2001


Your message with subj: kdevelop crashed when using menu to goto next, previous error line number

Sorry, but that backtrace isn't useful. Update and resubmit if this is 
still a problem.

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; 27 Jun 2001 05:03:14 +0000
Received: (qmail 25540 invoked by uid 33); 27 Jun 2001 05:03:13 -0000
Date: 27 Jun 2001 05:03:13 -0000
Message-ID: <20010627050313.25538.qmail at master.kde.org>
To: submit at bugs.kde.org
Subject: kdevelop crashed when using menu to goto next, previous error line number
From: crazycrusoe at yahoo.com

Package:           kdevelop
Version:           kdevelop 2.0 included in kde 2.2 beta 2 (using KDE 2.2.0 Alpha2)
Severity:          normal
Installed from:    Mandrake RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

after compiling a small proggy which had errors in it, i used the menu to go to error line number, it crashed, i dont have kde devel libs installed
but here is the backtrace

(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)...(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)...
0x412071d9 in wait4 () from /lib/libc.so.6
#0  0x412071d9 in wait4 () from /lib/libc.so.6
#1  0x41276f2c in __check_rhosts_file () from /lib/libc.so.6
#2  0x40980a68 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3
#3  0x4117bb68 in killpg () from /lib/libc.so.6
#4  0x088db378 in ?? ()
#5  0x3a435052 in ?? ()
 

(Submitted via bugs.kde.org)


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop-devel mailing list