[Digikam-devel] [digikam] [Bug 317943] (Auto) rotate/flip using EXIF Information destroys pictures

[Peter Albrecht]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #29 from Peter Albrecht <px79 at crazymonkeys.de> ---
(In reply to comment #27)
> (In reply to comment #26)
> > I thinking not about debug trace in fact, printed on the console.
> > I suspect more debug symbols included during compilation time.
> > Here with full debug symbol, i never reproduce this dysfunction.
> > In release compilation, all debug symbols are dropped and code in more
> > optimized (in speed in general). This can have any side effects...
> 
> What I did was enabling debug output with "kdebugdialog". Rebuilding digikam
> with debug symbols would be a lot more effort. ;)

Ok, I tried to build digikam with debug symbols, to help, finding out why you
can't reproduce the error.
On my gentoo system, I ...
   - added "-ggdb" to the CFLAGS in "make.conf"
   - added 'FEATURE="nostrip"' in "make.conf"
   - enabled the useflag "debug" for package "media-gfx/digikam"
  (according to http://www.gentoo.org/proj/en/qa/backtraces.xml)
Than I rebuild digikam. Now "/usr/bin/digikam" is 82 MByte large, so I guess,
there are a lot of debug symbols included. ;)

Additionally, I enabled every "*digikam*" setting in kdebugdialog.

Now I rerun my test of comment #28: "Doing one CTRL + SHIFT + "Cursor Right" on
my album of 415 images". This time I ended up with:
   - a total of 30 images destroyed
   - 16 "JpegRotator-XXXXXXX.digikamtempfile.jpg" files left after rotation
batch finished
   - 7 file of 0 Byte
   - 2 of those 0 Byte files with digikams thread-id attached to the filename
   - 2 files are larger than the larges original file

Another interesting fact: The destroyed images are not spread equally. Among
the 30 destroyed images, I have two blocks of 6 images with subsequent image
numbers:
   - IMG_7864.jpg to IMG_7869.jpg
   - IMG_8074.jpg to IMG_8079.jpg

=> To sum up: I still can reproduce this error with debug symbols enabled.

Do you have any idea, what I could test / debug / log next to help, find this
bug?

-- 
You are receiving this mail because:
You are the assignee for the bug.