| Summary: | crash in KDevelop::ConfigurableHighlightingColors::getAttribute | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | stompdagger1 |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | a.kulpinov, andysem, christopherheiny, gmikerub, gmrandazzo, gustavogx, ioannis.nousias, jarin.franek, jc1da.3011, jnem6403, neutronmama, pericles.luz, sebald |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | 4.1.0 | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
Valgrind log for the crashing kdevelop 4.1 New crash information added by DrKonqi valgrind log crash from valgrind report (no debug symbols though) valgrind (memcheck) log kdevelop run without crashing log New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
stompdagger1
2010-09-19 21:38:55 UTC
is this still an issue? Somehow I doubt it's on our side if launching kdev from the CLI makes it work. That indicates some bug on your environment setup. if you have more information showing it's a bug on our side after all, please reopen. *** Bug 254620 has been marked as a duplicate of this bug. *** *** Bug 254761 has been marked as a duplicate of this bug. *** As said in one of the duplicates: does it work when you properly set KDEDIRS and ran kbuildsycoca4 and launch kdevelop through the command line? See duplicate bug and this howto: http://www.kdevelop.org/mediawiki/index.php/KDevelop_4/compiling If it pertains, please send me a valgrind log: kdevelop --sessions # then find the {...hash...} for your session, now: KDEV_SESSION={...hash...} valgrind --track-origins=yes --num-callers=25 kdevelop.bin thanks Also, please try to reproduce in KDevelop 4.1. I run it again started with new session from the CLI. I'm just wondering, is it possible to remove KDevelop sessions? I have a huge list of them and I'd like to remove unused. *** Bug 255487 has been marked as a duplicate of this bug. *** I've tried a fix for kdev 4.1.1 / 4.2, please - if anyone can test current code from git do so and report back. The commit was: commit 96229871059b93cdb1e219602d7d257c4126dac8 Author: Milian Wolff <mail@milianw.de> Date: Thu Oct 28 14:05:12 2010 +0200 try to fix crash in KDevelop::ConfigurableHighlightingColors::getAttribute - make sure m_defaultColors is always initialized - add assertion in getter This is just a shot in the dark but it might be the right one, see esp. the queued connection in update() which might have lead to periods without an initialized m_defaultColors member. diff --git a/language/highlighting/colorcache.cpp b/language/highlighting/colorcache.cpp index 7bda401..9ee7c90 100644 --- a/language/highlighting/colorcache.cpp +++ b/language/highlighting/colorcache.cpp @@ -83,7 +83,7 @@ namespace KDevelop { ColorCache* ColorCache::m_self = 0; ColorCache::ColorCache(QObject* parent) - : QObject(parent), m_defaultColors(0), m_validColorCount(0), m_colorOffset(0), + : QObject(parent), m_defaultColors(new CodeHighlightingColors(this)), m_validColorCount(0), m_colorOffset(0), m_localColorRatio(0), m_globalColorRatio(0) { Q_ASSERT(m_self == 0); @@ -117,6 +117,7 @@ ColorCache::~ColorCache() { m_self = 0; delete m_defaultColors; + m_defaultColors = 0; } ColorCache* ColorCache::self() @@ -279,6 +280,7 @@ QColor ColorCache::blendLocalColor(QColor color) const CodeHighlightingColors* ColorCache::defaultColors() const { + Q_ASSERT(m_defaultColors); return m_defaultColors; } PS: a way to reproduce or a valgrind log from the crash would still be good. (In reply to comment #4) > As said in one of the duplicates: > > does it work when you properly set KDEDIRS and ran kbuildsycoca4 and launch > kdevelop through the command line? See duplicate bug and this howto: > > http://www.kdevelop.org/mediawiki/index.php/KDevelop_4/compiling > It seems working by set KDEDIRS and kbuildsycoca4 :| but i've to test it for one or two day before to sing victory. It's strange, because when i install the binary package from archlinux official repository, kbuildsycoca4 seems not to start. :| boh! if it persist i follow the steps below. > If it pertains, please send me a valgrind log: > > kdevelop --sessions # then find the {...hash...} for your session, now: > KDEV_SESSION={...hash...} valgrind --track-origins=yes --num-callers=25 > kdevelop.bin > > thanks > Thanks to you :) > Also, please try to reproduce in KDevelop 4.1. What???? This bug is made by KDevelop 4.1 :), sorry but i have not understood what you are trying to say :) END *** Bug 256132 has been marked as a duplicate of this bug. *** Created attachment 53276 [details]
New crash information added by DrKonqi
kdevelop (4.1.0) on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.7.0
- What I was doing when the application crashed:
Starting kdevelop. Was working in it yesterday, left few files open (no project), then shutdown comp. After KDE login, kdevelop was launched and produced SIGSEG. After trying manually from KDE menu, SIGSEG again.
-- Backtrace (Reduced):
#7 value (this=0x0, number=3) at /usr/include/QtCore/qhash.h:606
#8 operator[] (this=0x0, number=3) at /usr/include/QtCore/qhash.h:731
#9 KDevelop::ConfigurableHighlightingColors::getAttribute (this=0x0, number=3) at /usr/src/debug/kdevplatform-1.1.0/language/highlighting/configurablecolors.cpp:43
#10 0x06dcd013 in KDevelop::CodeHighlighting::attributeForType (this=0x904c690, type=KDevelop::HighlightingEnumContainer::LocalVariableType, context=KDevelop::HighlightingEnumContainer::DeclarationContext, color=...) at /usr/src/debug/kdevplatform-1.1.0/language/highlighting/codehighlighting.cpp:103
#11 0x06dcda5f in KDevelop::CodeHighlightingInstance::highlightDeclaration (this=0x9446d28, declaration=0x94441b8, color=...) at /usr/src/debug/kdevplatform-1.1.0/language/highlighting/codehighlighting.cpp:447
Created attachment 53289 [details]
Valgrind log for the crashing kdevelop 4.1
ok, I think the valgrind log you posted clarifies that I've fixed it. stay tuned for kdev 4.1.1 *** Bug 257586 has been marked as a duplicate of this bug. *** Created attachment 55053 [details]
New crash information added by DrKonqi
kdevelop (4.1.1) on KDE Platform 4.5.4 (KDE 4.5.4) using Qt 4.7.0
- What I was doing when the application crashed:
start kdevelop via synapse
This is on Ubuntu 10.10 with ppa backports for KDE, kdevelop 4.1.1. So it's not fixed yet.
It exhibits the same behavior as reported above. Kdevelop crashes when launched via menu or gnome-do/synapse, but not from CLI
-- Backtrace (Reduced):
#6 0x00007f1dc0966410 in KDevelop::CodeHighlightingInstance::highlightDUChain (this=0x3f40b70, context=<value optimized out>, colorsForDeclarations=) at ../../language/highlighting/codehighlighting.cpp:262
#7 0x00007f1dc09673ef in KDevelop::CodeHighlightingInstance::highlightDUChainSimple (this=0x3f40b70, context=0x380ec10) at ../../language/highlighting/codehighlighting.cpp:224
#8 0x00007f1dc0967302 in KDevelop::CodeHighlightingInstance::highlightDUChainSimple (this=0x3f40b70, context=0x3812c40) at ../../language/highlighting/codehighlighting.cpp:236
#9 0x00007f1dc096753b in KDevelop::CodeHighlightingInstance::highlightDUChain (this=0x3f40b70, context=0x3812c40) at ../../language/highlighting/codehighlighting.cpp:204
#10 0x00007f1dc09677c1 in KDevelop::CodeHighlighting::highlightDUChain (this=<value optimized out>, context=0x3812c40) at ../../language/highlighting/codehighlighting.cpp:173
starting via CLI with either 'setsid' or suffixed with '&', will cause the crash as well. please run it through valgrind then show me the log it produces when you hit the crash. Considering that it crashes somewhere else please put it into a new bug report. To run valgrind, use this: valgrind --track-origins=yes --num-callers=25 kdevelop thanks Created attachment 55082 [details]
valgrind log
Created attachment 55083 [details]
crash from valgrind report (no debug symbols though)
I'll include the log produced by valgrind and the crash report for that here, even though the latter one has no debug symbols. Can't find them for my distro (Ubuntu). Added the ddebs as well for the dbgsym.
Valgrind and gdb are mutually exclusive, the crash report is hence useless. And the memcheck log says KDevelop didn't crash, nor does it contain anything interesting. So please try again to actually reproduce the crash there, if you look at the log it doesn't say anything about KDevelop::CodeHighlightingInstance::highlightDUChain (which it should). Created attachment 55108 [details]
valgrind (memcheck) log
I see. Unfortunately that's all I get from memcheck. I'm including another produced log from valgrind, this time by streaming its output to a file (rather than using --log-file), including stderr. I don't get the KDevelop::CodeHighlightingInstance::highlightDUChain you mentioned, but you can see that kdevelop does crash.
Created attachment 55109 [details]
kdevelop run without crashing log
don't know if that helps, but I've also added the output I get from kdevelop when run via CLI (without & or setsid), which doesn't crash.
both are useless - I cannot help you without a way to reproduce (launching in the background with & or setsid both work for me). Anyways, this is unrelated to the original bug here - if you ever get more information, open a new bug. Just make sure you get a valgrind log that shows similar backtrace to the gdb crash, then you got something useful. The fact that this is not possible for you is really strange imo. Anyways, sorry - but nothing I can do. *** Bug 261453 has been marked as a duplicate of this bug. *** Created attachment 56311 [details]
New crash information added by DrKonqi
kdevelop (4.1.0) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1
- What I was doing when the application crashed:
Software:
XWin 1.9.3-2 (Cygwin/X)
Putty 0.60
Screen version 4.00.03 (FAU) 23-Oct-06
I tried to start kdevelop using PuTTY.
[user@localmachine ~]$ screen -dR
[user@localmachine ~]$ sudo su -
[root@localmachine ~]# echo $DISPLAY
localhost:10.0
[root@localmachine ~]# kdevelop
-- Backtrace (Reduced):
#6 value (this=0x0, number=6) at /usr/include/QtCore/qhash.h:606
#7 operator[] (this=0x0, number=6) at /usr/include/QtCore/qhash.h:731
#8 KDevelop::ConfigurableHighlightingColors::getAttribute (this=0x0, number=6) at /usr/src/debug/kdevplatform-1.1.0/language/highlighting/configurablecolors.cpp:43
#9 0x0000003a41bdece6 in KDevelop::CodeHighlighting::attributeForType (this=0x2cacbf0, type=KDevelop::HighlightingEnumContainer::ForwardDeclarationType, context=KDevelop::HighlightingEnumContainer::DeclarationContext, color=...) at /usr/src/debug/kdevplatform-1.1.0/language/highlighting/codehighlighting.cpp:103
#10 0x0000003a41bdf79b in KDevelop::CodeHighlightingInstance::highlightDeclaration (this=0x3b6dba0, declaration=<value optimized out>, color=...) at /usr/src/debug/kdevplatform-1.1.0/language/highlighting/codehighlighting.cpp:447
*** Bug 266350 has been marked as a duplicate of this bug. *** *** Bug 267541 has been marked as a duplicate of this bug. *** *** Bug 268235 has been marked as a duplicate of this bug. *** Created attachment 61086 [details]
New crash information added by DrKonqi
kdevelop (4.0.2 (using KDevPlatform 1.0.2)) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.0
- What I was doing when the application crashed:
- I was starting the KDevelop. It's important to say that only on te first startup the application crashs. It not happen on de second one.
-- Backtrace (Reduced):
#7 value (this=0x0, number=3) at /usr/include/qt4/QtCore/qhash.h:606
#8 operator[] (this=0x0, number=3) at /usr/include/qt4/QtCore/qhash.h:731
#9 KDevelop::ConfigurableHighlightingColors::getAttribute (this=0x0, number=3) at ../../language/highlighting/configurablecolors.cpp:41
#10 0x06cfce08 in KDevelop::CodeHighlighting::attributeForType (this=0x9074e18, type=KDevelop::HighlightingEnumContainer::LocalVariableType, context=KDevelop::HighlightingEnumContainer::DeclarationContext, color=...) at ../../language/highlighting/codehighlighting.cpp:101
#11 0x06cfdd9f in KDevelop::CodeHighlightingInstance::highlightDeclaration (this=0x93fe080, declaration=0x92e1110, color=...) at ../../language/highlighting/codehighlighting.cpp:445
|