[Kde-imaging] releasing kipi & co.

[Gilles Caulier]

2007/4/28, Angelo Naselli <anaselli at linux.it>:
>
> Alle sabato 28 aprile 2007, Aurélien Gâteau ha scritto:
> > On Saturday 28 April 2007 00:21:19 Angelo Naselli wrote:
> >
> > > I havn't seen any critical bugs except next one about HTML export:
> > > http://bugs.kde.org/show_bug.cgi?id=134300
> > > Please Aurelien can you tell me something about that?
> >
> > It really is strange. The HTML export plugin is not multithreaded, so it
> can't
> > be a multithread problem. The backtrace indicates it crashes in a
> kdDebug()
> > call from KIO::Scheduler, so I believe it's a kdelibs problem.
> Thanks Aurelien.
>
> Gilles since the reporter said he've chosen Album/export.... could it be
> related to
> digikam instead?
>
> Angelo


yes, you can see in the backtrace than the plugin have been started from
digiKam, but the crash is inside the plugin not digiKam.

I recommend two points :

- 1/ try to reproduce the crash under valgrind to have more debug
informations.
- 2/ try to use qDebug() instead kDdebug().

Nota : in digiKam 0.9.x we using a multithreaded wrapper for KDdebug()
because this one do not support multithreading. Personnaly i think than all
non graphics KDE API must be re-entrant. KDE API sound like very fragile
! We have a good experence MArcel & me about KDE API and multithreading
uncompatibility.

This problem about KDE API is a shame. and i'm affraid about KDE4. I'm sure
than we will discover a lots problems... QT API is more proffesional
development framework... Of course there are good ideas in KDE4 API, but I
recommend to take a care about to use it everywhere...

Gilles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-imaging/attachments/20070428/20240a0a/attachment.html