[Digikam-devel] [showfoto] [Bug 314547] showFoto: _XIOError in QSplashScreen::finish

[Christopher Yeleighton]

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

Christopher Yeleighton <giecrilj at stegny.2a.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |---

--- Comment #11 from Christopher Yeleighton <giecrilj at stegny.2a.pl> ---
(In reply to comment #9)
> If you media is not readable and lock your computer, well, it's a not a
> digiKam fault...


My media does not lock my computer, where did you get that?

Observe that:

1.  libexiv throws by design (see above).
2.  Throwing under Qt in the context where libexif throws is unsupported and
violates the contract (see above).
3. In an environment where throwing is unsupported (like e.g. in a C API
internally implemented in C++), any potential throws should be caught and
translated to a failure that the calling environment supports.
4. ShowFoto fails to protect Qt from libexif as it should.
5. Crashing in presence of a persistent storage failure is a bug.  Compare the
file utility; it does not crash and neither should ShowFoto.  

The bottom line is, scratches happen, crashes should not.

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