[Digikam-users] digikam 4.1 bugs

Anders Lund anders at alweb.dk
Mon Jul 28 10:56:56 BST 2014

On Mandag den 28. juli 2014 11:51:55, Remco Viƫtor wrote:
> On Monday 28 July 2014 11:03:49 Anders Lund wrote:
> > On Mandag den 21. juli 2014 18:19:52, Gilles Caulier wrote:
> > > Here, i'm in full debug mode, which introduce some small time
> > > latencies. which is enough to mask this kind of problem.
> > 
> > I don't think it is smart to require digikam being compiled in full debug
> mode
> > to work correctly!
> Gilles is not saying that you are required to build digikam in full debug
> mode, just that that is what he does, and that the build mode could change
> timings enough so that certain race conditions don't become visible (or
> much less often). That does not mean the races aren't there, just that they
> don't become visible.
> And that's typically the kind of bugs that you can get when switching to
> multithreaded, and they are particularly hard to debug...

If I can do anything to help, I will. I can install debug package etc, or even 
try to build digikam locally, if it can help :)


More information about the Digikam-users mailing list