[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: strange backtrace, crashing in qt
From:       tech () bishop ! dhs ! org
Date:       2002-12-12 6:32:42
[Download RAW message or body]

On Wed, Dec 11, 2002 at 10:18:14PM -0800, Robby Stephenson wrote:
> > > 1) I would stop the configure with an error if it doesn't find the
> > proper xml and xslt headers.  As it is, it continues on, and if you
> > aren't paying attention to the configure output, it's easy to miss that
> > you don't have what it needs to compile.
> 
> Good point, I wasn't paying attention to the autoconf language. Consider
> that fixed. I believe AC_MSG_WARN should just be changed to AC_MSG_ERROR,
> right?

I'm no autoconf wizard either, but I believe that is correct.

> > > 2) I am running debian/unstable, and I do *not* get a crash.  Instead, I
> > get no gui and all, and after a couple seconds, it just returns to the
> > command-line :-(  It outputs the following:
> >
> > [ david@debian ] $ bookcase
> > BCGroupView::slotShowCount
> > BCGroupView::setGroupAttribute -
> > Bookcase::updateCollectionToolBar
> > BCGroupView::setGroupAttribute - author
> > BCGroupView::locateItem() - adding new collection
> > BCGroupView::slotAddCollection
> > BCGroupView::slotAddCollection
> > Alarm clock
> 
> Hmmm, now I am really perplexed. I have no idea what that "Alarm clock" is
> doing there, it's nothing from my code.

Ouch :-(

> > I take that back.  If I run it under gdb, it is crashing, with an
> > identical backtrace.  I guess I'm used to the krash dialog coming up, so
> > I didn't expect it to just ... not appear.
> 
> I don't know why the krash dialog doesn't pop up either.

Is that a feature that should be inherited by all KApp's, or is it
something you need to turn on?  This question is for all listening, not
just Robby (as I'm getting the impression that neither one of us are
deeply experienced KDE programmers ;-)

> > Sorry this isn't of more help, but I tried...
> 
> Thanks for your feedback, it's good to have another datapoint, at least.
> Robby

I am using Karolina's debs (that means nothing to you, but you can ask
the other crashing debian users if they are too), which are compiled
using gcc 2.95.4.  Maybe this is a 3.2 vs. 2.95 thing? 

Also attached is the ldd output.  Maybe it's a bad/odd library?

libexslt.so.0 => /usr/lib/libexslt.so.0 (0x40012000)
libxslt.so.1 => /usr/lib/libxslt.so.1 (0x40021000)
libxml2.so.2 => /usr/lib/libxml2.so.2 0x4004a000)
libkhtml.so.4 => /usr/lib/libkhtml.so.4 (0x40100000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40308000)
libkdeprint.so.4 => /usr/lib/libkdeprint.so.4 (0x40326000)
libkparts.so.2 => /usr/lib/libkparts.so.2 (0x403bb000)
libkutils.so.1 => /usr/lib/libkutils.so.1 (0x403f0000)
libkio.so.4 => /usr/lib/libkio.so.4 (0x40402000)
libkdesu.so.4 => /usr/lib/libkdesu.so.4 (0x40640000)
libutil.so.1 => /lib/libutil.so.1 (0x40668000)
libfam.so.0 => /usr/lib/libfam.so.0 (0x4066b000)
libkdeui.so.4 => /usr/lib/libkdeui.so.4 (0x40674000)
libkdecore.so.4 => /usr/lib/libkdecore.so.4 (0x4086e000)
libDCOP.so.4 => /usr/lib/libDCOP.so.4 (0x409df000)
libdl.so.2 => /lib/libdl.so.2 (0x40a0d000)
libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0x40a10000)
libkdefx.so.4 => /usr/lib/libkdefx.so.4 (0x40a24000)
libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x40a4b000)
libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x40a51000)
libqt-mt.so.3 => /usr/lib/libqt-mt.so.3 (0x40a9a000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x4106e000)
libz.so.1 => /lib/libz.so.1 (0x4109b000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x410a9000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x410b6000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x41171000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x41179000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4118f000)
libm.so.6 => /lib/libm.so.6 (0x411df000)
libc.so.6 => /lib/libc.so.6 (0x41200000)
libaudio.so.2 => /usr/lib/libaudio.so.2 (0x41314000)
libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x41328000)
libmng.so.1 => /usr/lib/libmng.so.1 (0x41372000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x413b4000)
libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x4141a000)
libXft.so.1 => /usr/X11R6/lib/libXft.so.1 (0x4142e000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x41458000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
liblcms.so.1 => /usr/lib/liblcms.so.1 (0x414aa000) 

Best of luck, I know what it's like to try and trouble shoot really
weird things remotely.  It sucks :-(

D.A.Bishop
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]