doc-tab-bug in beta2??(was:Re: Problems with compiler option -g and configure)
Benoit Cerrina
benoit.cerrina at writeme.com
Tue Feb 1 21:27:48 GMT 2000
Hi,
I just took a look at your stack trace (I hadn't scrolled all the way down),
this is exactly the same bug we had. I know how to correct it and I will.
However it looks like the bypass which I found will need to be reimplemented
everytime we found a new manifestation of it. What I had corrected before was:
bring the outputview very high to make sure the docview scrollbar will be
there, switch to something else than docview, reload or refresh the project.
Switch to the docview (no need to hurry).
Ben
On lun, 31 jan 2000, you wrote:
> On Sam, 29 Jan 2000 you wrote:
> > On Sat, 29 Jan 2000, Joachim Ansorg wrote:
> [snip]
> > > BTW, KDevelop does crash again (only sometime) if I click on the Doc Tab.
> >
> > Oh no :(
> >
> > Are you on cvs version or released beta1?
> > What did you do just before this? compile? load a project?
> > Don't happen to have a backtrace?
> >
> > Umm, it's a difficult one because its not reproducable. Or rather since that
> > last fix a week ago, I've not been able to crash this. I'm guessing it'll be
> > the same qt bug being triggered in a different way, but ...
> [snap]
>
> Hi,
> it seems that your talking about the doc-tab-crash-bug ("an old friend of
> mine"). The doc-tab-bug is 100% reproducable on my system.
> (In Version 1.1beta1;CVSUP;and still in beta2)
>
> Just do the following:
> ->disable the outputview
> ->click the doctab
> ->expand some listitems until the vertical scrollbar appears
> ->load a project
> ->while loading, click docbrowsertab, then immediatly outputview toolbutton
> ->crash !
>
> The backtrace looks different from crash to crash (I added three of them),
> but is almost the same in any version I tried.
>
> One guy on this list told me, that he can´t reproduce this.
>
> Just some thoughts:
>
> - If you run Kdevelop with a high screen resolution (e.g. 1600x1200 pixel), you
> won´t run into this bug very often, because the listview can contain more items?
> But the bug should be reproducable if you expand the listview like I said
> before.
> - Maybe this bug occurs more often on slow machines? (I´m running an old i586
> here)
> - Maybe there is something wrong with my qt-libs? (But the other KDE-apps run
> stable!?)
> - Maybe I´m doing something real stupid?
>
> My wish:
>
> Can anyone try this, and confirm this bug (it only takes a minute)?
> I just would like to know, whether I´m the only one with this problem.
>
> Sorry for for this mega-mail, but I thought it could be helpful.
>
> Bye M.D.
>
>
> i586, SuSe 6.1, egcs-2.91.66
> ----------------------------------------
> Program received signal SIGSEGV, Segmentation fault.
> 0x40168e1f in QListView::drawContentsOffset ()
> (gdb) bt
> #0 0x40168e1f in QListView::drawContentsOffset ()
> #1 0x40187f9b in QScrollView::viewportPaintEvent ()
> #2 0x40187dbd in QScrollView::eventFilter ()
> #3 0x4016a7fe in QListView::eventFilter ()
> #4 0x4011a3ea in QObject::activate_filters ()
> #5 0x40130fd5 in QWidget::event ()
> #6 0x400f5400 in QApplication::notify ()
> #7 0x401c368c in QWidget::repaint ()
> #8 0x401c420f in QWidget::setGeometry ()
> #9 0x40186efe in QScrollView::updateScrollBars ()
> #10 0x401888db in QScrollView::resizeContents ()
> #11 0x4016a165 in QListView::updateGeometries ()
> #12 0x4016a0ce in QListView::show ()
> #13 0x40438565 in KTabCtl::showTab ()
> #14 0x4011c677 in QObject::activate_signal ()
> #15 0x401dc7d4 in QTabBar::selected ()
> #16 0x40193154 in QTabBar::setCurrentTab ()
> #17 0x40192fc5 in QTabBar::setCurrentTab ()
> #18 0x8092e45 in _start ()
> #19 0x807c439 in _start ()
> -------------------------------------
> Program received signal SIGSEGV, Segmentation fault.
> 0x4016c146 in QListView::itemMargin ()
> (gdb) bt
> #0 0x4016c146 in QListView::itemMargin ()
> #1 0x40167247 in QListViewItem::paintCell ()
> #2 0x40168e24 in QListView::drawContentsOffset ()
> #3 0x40187f9b in QScrollView::viewportPaintEvent ()
> #4 0x40187dbd in QScrollView::eventFilter ()
> #5 0x4016a7fe in QListView::eventFilter ()
> #6 0x4011a3ea in QObject::activate_filters ()
> #7 0x40130fd5 in QWidget::event ()
> #8 0x400f5400 in QApplication::notify ()
> #9 0x401c368c in QWidget::repaint ()
> #10 0x401c420f in QWidget::setGeometry ()
> #11 0x40186efe in QScrollView::updateScrollBars ()
> #12 0x401888db in QScrollView::resizeContents ()
> #13 0x4016a165 in QListView::updateGeometries ()
> #14 0x4016a0ce in QListView::show ()
> #15 0x40438565 in KTabCtl::showTab ()
> #16 0x4011c677 in QObject::activate_signal ()
> #17 0x401dc7d4 in QTabBar::selected ()
> #18 0x40193154 in QTabBar::setCurrentTab ()
> #19 0x40192fc5 in QTabBar::setCurrentTab ()
> #20 0x8092e45 in _start ()
> #
> -----------------------------------
> Program received signal SIGSEGV, Segmentation fault.
> 0x4016726d in QListViewItem::paintCell ()
> (gdb) bt
> #0 0x4016726d in QListViewItem::paintCell ()
> #1 0x40168e24 in QListView::drawContentsOffset ()
> #2 0x40187f9b in QScrollView::viewportPaintEvent ()
> #3 0x40187dbd in QScrollView::eventFilter ()
> #4 0x4016a7fe in QListView::eventFilter ()
> #5 0x4011a3ea in QObject::activate_filters ()
> #6 0x40130fd5 in QWidget::event ()
> #7 0x400f5400 in QApplication::notify ()
> #8 0x401c368c in QWidget::repaint ()
> #9 0x401c420f in QWidget::setGeometry ()
> #10 0x40186efe in QScrollView::updateScrollBars ()
> #11 0x401888db in QScrollView::resizeContents ()
> #12 0x4016a165 in QListView::updateGeometries ()
> #13 0x4016a0ce in QListView::show ()
> #14 0x40438565 in KTabCtl::showTab ()
> #15 0x4011c677 in QObject::activate_signal ()
> #16 0x401dc7d4 in QTabBar::selected ()
> #17 0x40193154 in QTabBar::setCurrentTab ()
> #18 0x40192fc5 in QTabBar::setCurrentTab ()
> #19 0x8092e45 in _start ()
--
Benoit Cerrina
More information about the KDevelop
mailing list