Le Vendredi 13 Janvier 2006 16:13, vous avez écrit :
> Hi,
>
> could you test it?
Hum, busy actually. If you can do it and give me a backtrace using valgring...
>
> Unfortunately I don't have the tools currently to do that and also only
> little time.
(:=))). Make a new file in B.K.O if necessary. I will unforget it like this.
>
> Btw: Until now I have only seen the export to static HTML-Pages. Then there
> is the KIPI script for exporting to "gallery" php image gallery but are
> there currently any further possibilities to export at least digikam
> comments (better would be even kind of tag-structure export) to a php/sql
> image database?
Take a look in B.K.O. There are any files about. Please adding your entry if
necessay.
Gilles
>
> Martin
>
> On Tuesday 10 January 2006 12:29, Gilles Caulier wrote:
> > The better way to check memory leak is to use valgrind tool like this :
> >
> > valgrind --tool=memcheck --leak-check=full --error-limit=no digikam
> >
> > note that digikam must be compiled using all debug information to get
> > witch source code line(s) are in default.
> >
> > I had no PTP camera, only USB mass storage here to test.
> >
> > When you run digikam under valgrind, the speed is very low ( divide per
> > 15 approximativly), but speed performance is not the issue with valgrind
> > because it check all memory allocations/desallocations completed by the
> > program.
> >
> > Reproduce all action in digiKam using valgrind, all post all error
> > console messages provides by valgrind.
> >
> > Thanks in advance.
--
Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
