[KimDaBa] Re: Crash after changing XML in current CVS

[Walter Francis]

Terrific!  Hope to see it in cvs soon.

I didn't get a chance to play with it much because it was crashing,
but is the implimentation of tagging images by letters the same as the
2005-01-20 tarball you have on the webpage?  I've experimented a
little and I'm not sure how to really use it.  :)  If I type a letter
when viewing an image, it shows up in the keywords and such, but how
to associate that with a particular keyword?

Might just not be completed yet.


On Sun, 6 Mar 2005 16:02:27 -0100, "Jesper K. Pedersen"
<blackie at blackie.dk> wrote:
> I've just fixed this bug. It is on my harddisk now, and will be checked in
> as 
> soon as I remember to do so (Are currently in a train without internet 
> access).
> 
> Cheers
> Jesper.
> 
> On Monday 28 February 2005 22:49, Walter Francis wrote:
> | Upon your suggestion, I decided to try out the latest CVS and compiled
> | it as described on the webpage.  Had to do a few adjustments with
> | header files (wasn't seeing them in /usr/include/kde/* so I had to
> | copy them to ., worked okay), but otherwise no problems compiling.
> |
> | When I first load KimDaBa it warns of images without dates that will
> | affect the date bar, so I did the suggested search of images, re-read
> | the dates from the exit, and sorted the images.  Looked right, but
> | when I save and exit, it crashes on startup.  Reproduced it a few
> | times now.  If I don't sort the images, it doesn't seem to crash on
> | restart.
> |
> | Further investigation shows that if the database is changed and the
> | new KimDaBa saves it in any way, it crashes on the next startup.
> |
> | Any suggestions?  It looks nice :)
> |
> | # kimdaba
> | List of new Images:
> | KCrash: Application 'kimdaba' crashing...
> |
> | Output from the KDE Crash handler..
> |
> | Using host libthread_db library "/lib/tls/libthread_db.so.1".
> | `shared object read from target memory' has disappeared; keeping its
> | symbols. [Thread debugging using libthread_db enabled]
> | [New Thread -1208919840 (LWP 23995)]
> | [KCrash handler]
> | #4  0x0809dc40 in ImageDate::min ()
> | #5  0x080b49cf in ImageDB::mergeNewImagesInWithExistingList ()
> | #6  0x080b6f07 in ImageDB::loadExtraFiles ()
> | #7  0x080b7174 in ImageDB::slotRescan ()
> | #8  0x0808cdf2 in MainView::delayedInit ()
> | #9  0x0808df38 in MainView::qt_invoke ()
> | #10 0x4384300e in QObject::activate_signal ()
> |    from /usr/lib/qt-3.1//lib/libqt-mt.so.3
> | #11 0x43b74e3d in QSignal::signal () from
> | /usr/lib/qt-3.1//lib/libqt-mt.so.3 #12 0x4385bded in QSignal::activate ()
> | from /usr/lib/qt-3.1//lib/libqt-mt.so.3 #13 0x43862fff in
> | QSingleShotTimer::event ()
> |    from /usr/lib/qt-3.1//lib/libqt-mt.so.3
> | #14 0x437e44da in QApplication::internalNotify ()
> |    from /usr/lib/qt-3.1//lib/libqt-mt.so.3
> | #15 0x437e466a in QApplication::notify ()
> |    from /usr/lib/qt-3.1//lib/libqt-mt.so.3
> | #16 0x41f0c458 in KApplication::notify () from /usr/lib/libkdecore.so.4
> | #17 0x437d88cb in QEventLoop::activateTimers ()
> |    from /usr/lib/qt-3.1//lib/libqt-mt.so.3
> | #18 0x4379236e in QEventLoop::processEvents ()
> |    from /usr/lib/qt-3.1//lib/libqt-mt.so.3
> | #19 0x437f9a95 in QEventLoop::enterLoop ()
> |    from /usr/lib/qt-3.1//lib/libqt-mt.so.3
> | #20 0x437f99ee in QEventLoop::exec () from
> | /usr/lib/qt-3.1//lib/libqt-mt.so.3 #21 0x437e3813 in QApplication::exec
> ()
> | from /usr/lib/qt-3.1//lib/libqt-mt.so.3 #22 0x0806cb4c in main ()
> 
> -- 
> Jesper K. Pedersen          |  Klarälvdalens Datakonsult
> Senior Software Engineer    |  www.klaralvdalens-datakonsult.se
> Prinsensgade 4a st.         |
> 9800 Hjørring               |  Platform-independent
> Denmark                     |  software solutions
> 
> 
> 
> !DSPAM:422c4610226361636718461!
> 
> 

-- 
Walter Francis
http://khayts.us
http://theblackmoor.net
http://unlimitedphoto.com                Powered by Fedora Core 3