Bug#36750: marked as done (dlopen causes program crash in debugging) by John Firebaugh <jfirebaugh at kde.org>
owner at bugs.kde.org
Sat Aug 31 07:21:40 UTC 2002
Your message with subj: dlopen causes program crash in debugging
Thank you for your bug report.
This bug can not be reproduced using the current development (CVS) version of
KDE. This suggests that the bug has already been fixed. The bug report will
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)
(Complete bug history is available at http://bugs.kde.org/db/36/36750.html)
Received: (at submit) by bugs.kde.org; 3 Jan 2002 08:39:37 +0000
Received: (qmail 11578 invoked by uid 33); 3 Jan 2002 08:39:37 -0000
Date: 3 Jan 2002 08:39:37 -0000
Message-ID: <20020103083937.11577.qmail at master.kde.org>
To: submit at bugs.kde.org
Subject: dlopen causes program crash in debugging
From: richard at garandnet.net
Version: 2.0.1 (using KDE 2.2.1 )
Installed from: Mandrake RPMs
Compiler: gcc version 2.96 20000731 (Mandrake Linux 8.1 2.96-0.62mdk)
OS: Linux (i686) release 2.4.8-26mdk
When debugging a program in KDevelop, dlopen never returns (with calls to dlerror() and __dl_catch_error()). When I run the program normally (from the IDE), this function call works fine.
(Submitted via bugs.kde.org)
(Called from KBugReport dialog. Fields KDE Version manually changed)
More information about the KDevelop-devel