/usr/share/doc/libbarry-dev/Exceptions is in libbarry-dev 0.18.5-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 | The Barry library has the following exception hierarchy:
- std::exception
- std::logic_error
- std::runtime_error
- Barry::Error
- Usb::Error
- Usb::Timeout
- Barry::BadPassword
- Barry::SocketCloseOnOpen
- Barry::BadData
- Barry::BadSize
- Barry::ConfigFileError
- Barry::ErrnoError
- Barry::ConfigFileError
- Barry::BadPackedFormat
- Barry::BadPacket
- Barry::ConvertError
- Barry::BackupError
- Barry::RestoreError
- Barry::JDWP::Error
- Barry::JDWP::Timeout
- Barry::PinNotFound
- Barry::ReturnCodeError
Usb::Error
All specific USB error exceptions will be derived from
this class. Where possible, this class also stores the
specific return code from the libusb API, to allow
fine grained error handling.
Barry::Error
All specific Barry error exceptions will be derived from
this class. This can be thrown from anywhere inside Barry.
std::bad_alloc
There is also the remote possibility that there will be memory
exceptions from a call to 'new'. In that case, std::bad_alloc
will be thrown by the standard C++ libraries. Barry does not
catch these errors.
std::logic_error
Assert-like errors will cause std::logic_error to be thrown.
Barry does sometimes throw these, but they should be be
exceedingly rare.
All of the above exceptions (from std, Barry, and Usb namespaces)
are derived from std::exception, so they can all be caught in one
statement for the efficient and lazy. :-)
|