Catch std::exception in iptcprint

[kevinbackhouse]

The main function in the iptcprint sample program catches Exiv2::AnyError but not std::exception. The poc attached to #2050 is a bogus image file that triggers a std::overflow_error in this call to Safe::add():

exiv2/src/rafimage.cpp

Line 308 in 0b17cc3

enforce(Safe::add(jpg_img_off_u32, jpg_img_len_u32) <= io_->size(), kerCorruptedMetadata);

In the exiv2 application, we catch those exceptions and print an error message. We just need to do the same in this sample application.

I also changed the error return code to 1, because -1 is non-standard.

[codecov]

Codecov Report

Merging #2111 (571c84f) into main (0b17cc3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2111   +/-   ##
=======================================
  Coverage   63.80%   63.80%           
=======================================
  Files          96       96           
  Lines       19169    19169           
  Branches     9772     9772           
=======================================
  Hits        12230    12230           
  Misses       4658     4658           
  Partials     2281     2281           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0b17cc3...571c84f. Read the comment docs.

[piponazo]

Could we use here EXIT_FAILURE? I like to use those exit values macros for making the code more readable:

https://en.cppreference.com/w/cpp/utility/program/EXIT_status

It is also fine for me if you want to merge this directly, and we can do a whole replacement of exit values in another PR