https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #17 from k...@binkmail.com --- Sorry guys. Guess I should have tried this sooner. I ran digikam with sysinternals dbgview and it logged a few hundred lines. TIFFPrintDirectory(tif, stdout, 0); Is going to stdout and QT under windows somehow doesn't do stdout. Searching about QT and stdout I read a QT application will 'do' stdout when directed to a file so I ran digikam 7.5 from the command line with stdout directed to a file. In digikam I full screen viewed a 266MB tiff file produced by photoshop and quit. The redirected stdout file is 2.8GB. I have trouble viewing this file, probably because it only has 775 lines some of which must be 100s of MB long. I do see this for example PhotoshopLayerData: 0x41,0x64,0x6f,0x62,0x65,0x20,0x50,0x68,0x6f,0x74,0x6f,0x73,0x68,0x6f,0x70,0x20,0x44,0x6f,0x63,0x70x0,0xc2,0x0,0xc2, So it looks like TIFFPrintDirectory(tif, stdout, 0); is dumping all or large parts of the tiff in comma separated hex. TIFFPrintDirectory is the real problem not debug logging. -- You are receiving this mail because: You are watching all bug changes.