Library Version 11.2.5.3

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +

Prev	Chapter 3. - Debugging Applications -	Chapter 3. Debugging Applications	Next

@@ -38,32 +36,44 @@

Normally, when an error occurs in the Berkeley DB library, an integer value -(either a Berkeley DB specific value or a system errno value) is -returned by Berkeley DB. In some cases, however, this value may be -insufficient to completely describe the cause of the error, especially -during initial application debugging.

Most Berkeley DB errors will result in additional information being written -to a standard file descriptor or output stream. Additionally, Berkeley DB can -be configured to pass these verbose error messages to an application -function. There are four methods intended to provide applications with -additional error information: -DB_ENV->set_errcall(), DB_ENV->set_errfile(), -DB_ENV->set_errpfx() and DB_ENV->set_verbose().

The Berkeley DB error-reporting facilities do not slow performance or -significantly increase application size, and may be run during normal -operation as well as during debugging. Where possible, we recommend -these options always be configured and the output saved in the -filesystem. We have found that this often saves time when debugging -installation or other system-integration problems.

In addition, there are three methods to assist applications in -displaying their own error messages: db_strerror(), DB_ENV->err(), -and DB_ENV->errx(). The first is a superset of -the ANSI C strerror function, and returns a descriptive string for any -error return from the Berkeley DB library. The DB_ENV->err() and -DB_ENV->errx() methods use the error message configuration options -described previously to format and display error messages to appropriate -output devices.

+ Normally, when an error occurs in the Berkeley DB library, + an integer value (either a Berkeley DB specific value or a + system errno value) is returned by Berkeley + DB. In some cases, however, this value may be insufficient to + completely describe the cause of the error, especially during + initial application debugging. +

+ Most Berkeley DB errors will result in additional + information being written to a standard file descriptor or + output stream. Additionally, Berkeley DB can be configured to + pass these verbose error messages to an application function. + There are four methods intended to provide applications with + additional error information: DB_ENV->set_errcall(), + DB_ENV->set_errfile(), DB_ENV->set_errpfx() and DB_ENV->set_verbose(). +

+ The Berkeley DB error-reporting facilities do not slow + performance or significantly increase application size, and + may be run during normal operation as well as during + debugging. Where possible, we recommend these options always + be configured and the output saved in the filesystem. We have + found that this often saves time when debugging installation + or other system-integration problems. +

+ In addition, there are three methods to assist applications + in displaying their own error messages: db_strerror(), + DB_ENV->err(), and DB_ENV->errx(). The + first is a superset of the ANSI C strerror function, and + returns a descriptive string for any error return from the + Berkeley DB library. The DB_ENV->err() and + DB_ENV->errx() methods use the + error message configuration options described previously to + format and display error messages to appropriate output + devices. +