[Bug 51652] New: Configure Gideon... crashes when missing "Last Project" in gideonrc
Sebastian Kratzert
skratzert at gmx.de
Sun Dec 8 18:29:02 UTC 2002
On Sunday 08 December 2002 15:44, Johan "ThelmXn" wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=51652
> Summary: Configure Gideon... crashes when missing "Last Project"
> in gideonrc
> Product: kdevelop
> Version: unspecified
> Platform: Debian testing
> OS/Version: Linux
> Status: UNCONFIRMED
> Severity: crash
> Priority: NOR
> Component: general
> AssignedTo: kdevelop-devel at barney.cs.uni-potsdam.de
> ReportedBy: jth at home.se
>
>
> Version: gideon (using KDE KDE 3.0.9)
> Installed from: Debian testing/unstable Packages
> Compiler: gcc version 2.95.4 20011002 (Debian prerelease)
> OS: Linux
>
> Was unable to Settings->Configure Gideon... after installation.
> But after I created a project it was ok. Traced it to "Last Project"
> in General Options.
>
> .kde/share/config/gideonrc
>
> [General Options]
> Last Project=/space/hello/hello.kdevelop
>
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 8108)]
> 0x40df7106 in QDomDocument::documentElement () from /usr/lib/libqt-mt.so.3
> (gdb) bt
> #0 0x40df7106 in QDomDocument::documentElement () from
> /usr/lib/libqt-mt.so.3 #1 0x40371335 in DomUtil::elementByPath (doc=@0x0,
> path=@0xbfffedcc) at ../../../lib/util/domutil.cpp:30 #2 0x40371714 in
> DomUtil::readListEntry (doc=@0x0, path=@0xbfffedcc, tag=@0xbfffedd0) at
> ../../../lib/util/domutil.cpp:86
> #3 0x431e6ede in DocTreeGlobalConfigWidget::DocTreeGlobalConfigWidget
> (this=0x83d5fe8, part=0x820da60, widget=0x81cab70, parent=0x83d5ae0,
> name=0x431f7bb1 "doc tree config widget") at
> ../../../parts/doctreeview/doctreeglobalconfigwidget.cpp:39 #4 0x431daa08
> in DocTreeViewPart::configWidget (this=0x820da60, dlg=0xbfffef90) at
> ../../../parts/doctreeview/doctreeviewpart.cpp:129
> #5 0x431dba2d in DocTreeViewPart::qt_invoke (this=0x820da60, _id=3,
> _o=0xbfffeef0) at doctreeviewpart.moc:112 #6 0x40c38d13 in
> QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #7 0x0808468d in
> KDevCore::configWidget (this=0x811e058, t0=0xbfffef90) at kdevcore.moc:153
> #8 0x080755b0 in TopLevelSDI::slotSettings (this=0x814d4d8) at
> ../../src/core.h:30 #9 0x0807622b in TopLevelSDI::qt_invoke
> (this=0x814d4d8, _id=82, _o=0xbffff0e4) at toplevel_sdi.moc:158 #10
> 0x40c38c79 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11
> 0x40c38bbe in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #12
> 0x4070e204 in KAction::activated () from /usr/lib/libkdeui.so.4 #13
> 0x40704252 in KAction::slotActivated () from /usr/lib/libkdeui.so.4 #14
> 0x4070e402 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4 #15
> 0x40c38c79 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #16
> 0x40e99553 in QSignal::signal () from /usr/lib/libqt-mt.so.3
> #17 0x40c4e2f5 in QSignal::activate () from /usr/lib/libqt-mt.so.3
> #18 0x40cffa9f in QPopupMenu::mouseReleaseEvent () from
> /usr/lib/libqt-mt.so.3 #19 0x40c634d6 in QWidget::event () from
> /usr/lib/libqt-mt.so.3
> #20 0x40be6c13 in QApplication::internalNotify () from
> /usr/lib/libqt-mt.so.3 #21 0x40be66bb in QApplication::notify () from
> /usr/lib/libqt-mt.so.3 #22 0x408a4e2a in KApplication::notify () from
> /usr/lib/libkdecore.so.4 #23 0x40b9bfe9 in QETWidget::translateMouseEvent
> () from /usr/lib/libqt-mt.so.3 #24 0x40b9a658 in
> QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #25 0x40bab942
> in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #26 0x40bf827e
> in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #27 0x40bf81db in
> QEventLoop::exec () from /usr/lib/libqt-mt.so.3
> #28 0x40be6d6a in QApplication::exec () from /usr/lib/libqt-mt.so.3
> #29 0x080623ac in main (argc=1, argv=0xbffffa54) at ../../src/main.cpp:78
This is my fault.
There is an unchecked 0 pointer in DoctreeGlobalConfigWidget. Additionally
doctreeview needs many changes for the new config-api. It is currently wrong
to read project dependent options in the global config dialog.
Unfortunately i will only have time for the restructoring from next weekend
on.
--
bye,
Sebastian
More information about the KDevelop-devel
mailing list