Bug 137610
Summary: | Kdevelop crashes in FC3rc3. Looks like glibc related. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kim Lux <lux> |
Component: | kdevelop | Assignee: | Than Ngo <than> |
Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-05 18:16:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kim Lux
2004-10-29 19:18:20 UTC
The chances of this being a glibc bug rather than KDE/Qt bug are really low, as in, there is absolutely no indication from the above report that would point to glibc. It crashes at the same address in memcpy() every time. I had a really obscure QT crash in FC3T3 when I first installed it. I had the backtrace on it until a few hours ago. I deleted it. I left the qt bt out because I didn't think it was relevant. When you mean KDE to you mean as in kdebase or kdevelop ? Do you think qt is giving memcpy and invalid pointer ? I don't understand why it fails silently. What is killing the process ? Is it killing itself ? I'm using kdebug-dialog --full and I'm not seeing any asserts going off anywhere. Is there a debug version of kde, qt or glibc I should be running to get more info ? Look what I found: Using host libthread_db library "/lib/tls/libthread_db.so.1". [KCrash handler] #5 0x0676b207 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #6 0x000001f4 in ?? () from /lib/libdl.so.2 #7 0x067686d1 in QString::operator+= () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 I've reported this to kdev's bugzilla. It is bug# 92560. The root cause of this problem was found in kdevelop. Although I was reassured that the problem was isolated to my use of FC3, a kdev developer found a bug that had nothing to do with FC3. |