Bug#26502: marked as done (kdevelop not closing sockets) by John Firebaugh <jfirebaugh at kde.org>

Stephan Kulow owner at bugs.kde.org
Sat Aug 31 04:57:05 UTC 2002

Your message with subj: kdevelop not closing sockets

Thank you for your bug report.
The bug that your reported no longer applies to the latest development (CVS) 
version of KDE. This is most probably because the bug has been fixed, the 
application has been substantially modified, or the application no longer 
exists. The bug report will be closed.

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)

(Complete bug history is available at http://bugs.kde.org/db/26/26502.html)

Received: (at submit) by bugs.kde.org; 31 May 2001 22:58:30 +0000
Received: (qmail 6088 invoked by uid 33); 31 May 2001 22:58:30 -0000
Date: 31 May 2001 22:58:30 -0000
Message-ID: <20010531225830.6087.qmail at master.kde.org>
To: submit at bugs.kde.org
Subject: kdevelop not closing sockets
From: brettelm at yahoo.com

Package:           kdevelop
Version:           2.0 (using KDE 2.2.0 \6alpha1)
Severity:          normal
Installed from:    Red Hat Linux 7.1
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81)
OS:                Linux (i686) release 2.4.3
OS/Compiler notes: 

When I run the program I am developing from within KDevelop, it does not close any open sockets when the program exits.  

The expected behavior is for the operating system to close any remaining open file/socket descriptors upon program termination, but this does not appear to happen when the program is run from within Kdevelop.

You can remedy this by restarting KDevelop, as that forces the program to release open descriptors.

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

More information about the KDevelop-devel mailing list