KDE/kdevplatform/shell

Andreas Pakulat apaku at gmx.de
Thu Jun 19 07:54:41 UTC 2008


On 19.06.08 10:25:09, Hamish Rodda wrote:
> On Thursday 19 June 2008 07:35:32 Andreas Pakulat wrote:
> > On 18.06.08 03:21:51, Hamish Rodda wrote:
> > > SVN commit 821654 by rodda:
> > >
> > > Complete the code displaying line,column status information on the status
> > > bar for the active view
> >
> > One of these three completely broke kdevelop for me (this happened during
> > startup):
> >
> > #0  0xb6072f67 in QObject::parent (this=0xddbbdb8)
> >     at /home/andreas/qt-copy/include/QtCore/qobject.h:236
> > #1  0xb607a345 in
> > Sublime::MainWindowPrivate::IdealToolViewCreator::operator()
> > (this=0xbf9de978, view=0xe0a70c0, position=Sublime::Right)
> >     at /home/andreas/KDE-work/4.0/kdevplatform/sublime/mainwindow_p.cpp:118
> > #2  0xb607d338 in
> > Sublime::Area::walkToolViews<Sublime::MainWindowPrivate::IdealToolViewCreat
> >or> ( this=0x81cfe78, op=@0xbf9de978, positions=@0xbf9de974)
> >     at /home/andreas/KDE-work/4.0/kdevplatform/sublime/areawalkers.h:59
> > #3  0xb607a5fb in Sublime::MainWindowPrivate::reconstruct (this=0x8187880)
> >     at /home/andreas/KDE-work/4.0/kdevplatform/sublime/mainwindow_p.cpp:187
> > #4  0xb6076f22 in Sublime::MainWindow::setArea (this=0x81803b8,
> > area=0x81cfe78) at
> > /home/andreas/KDE-work/4.0/kdevplatform/sublime/mainwindow.cpp:71 #5 
> > 0xb607da74 in Sublime::MainWindowOperator::setArea (this=0x8168f10,
> > w=0x81803b8, area=0x81cfe78) at
> > /home/andreas/KDE-work/4.0/kdevplatform/sublime/mainwindowoperator.cpp:27
> > #6  0xb607243d in Sublime::Controller::showAreaInternal (this=0x8168f10,
> > area=0x81cfe78, mainWindow=0x81803b8) at
> > /home/andreas/KDE-work/4.0/kdevplatform/sublime/controller.cpp:144 #7 
> > 0xb6072c0d in Sublime::Controller::showArea (this=0x8168f10,
> > areaTypeId=@0xbf9deba0, mainWindow=0x81803b8) at
> > /home/andreas/KDE-work/4.0/kdevplatform/sublime/controller.cpp:177 #8 
> > 0xb7c8d49c in KDevelop::UiController::loadAllAreas (this=0x8168f10,
> > config=@0xbf9dec58) at
> > /home/andreas/KDE-work/4.0/kdevplatform/shell/uicontroller.cpp:530 #9 
> > 0xb7c8c0ff in KDevelop::CorePrivate::initialize (this=0x816e968) at
> > /home/andreas/KDE-work/4.0/kdevplatform/shell/core.cpp:85
> > #10 0xb7c8b751 in KDevelop::Core::initialize ()
> >     at /home/andreas/KDE-work/4.0/kdevplatform/shell/core.cpp:117
> > #11 0x0804e08a in main (argc=2, argv=0xbf9df184)
> >     at /home/andreas/KDE-work/4.0/kdevelop/src/main.cpp:141
> >
> > Of course removing kdeveloprc helps (or rather removing the stored area
> > layouts), but a small note on kdevelop-devel or at least in the commit
> > log that a commit breaks restoring areas with existing configs would be
> > nice ;) Just in case this helps, here's the diff between the original
> > config and what kdevelop wrote after I removed area layouts and let it
> > close once (.new is the new version of course):
> 
> I can't see how my commits could have done this, and it was not a problem for 
> me, so I suggest you try to debug further (valgrind log?)

I'll try to do that later tonight, but as far as I could see in the diff
of the kdeveloprc files the format of area layout changed and seemingly
broke loading it. And there where no changes in shell/sublime between my
crashing build and the last working build...

Its not that big a deal, we don't guarantee "compatibility" of the
KConfig files yet so deleting them every once in a while is expected.

Andreas

-- 
You will forget that you ever knew me.




More information about the KDevelop-devel mailing list