diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/installation/debug_runtime.html | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/installation/debug_runtime.html')
| -rw-r--r-- | docs/installation/debug_runtime.html | 70 |
1 files changed, 40 insertions, 30 deletions
diff --git a/docs/installation/debug_runtime.html b/docs/installation/debug_runtime.html index 58a5beec..0708f684 100644 --- a/docs/installation/debug_runtime.html +++ b/docs/installation/debug_runtime.html @@ -14,7 +14,7 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> @@ -22,9 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="debug_compile.html">Prev</a> </td> - <th width="60%" align="center">Chapter 3. - Debugging Applications - </th> + <th width="60%" align="center">Chapter 3. Debugging Applications </th> <td width="20%" align="right"> <a accesskey="n" href="debug_printlog.html">Next</a></td> </tr> </table> @@ -38,32 +36,44 @@ </div> </div> </div> - <p>Normally, when an error occurs in the Berkeley DB library, an integer value -(either a Berkeley DB specific value or a system <code class="literal">errno</code> 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.</p> - <p>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: -<a href="../api_reference/C/envset_errcall.html" class="olink">DB_ENV->set_errcall()</a>, <a href="../api_reference/C/envset_errfile.html" class="olink">DB_ENV->set_errfile()</a>, -<a href="../api_reference/C/envset_errpfx.html" class="olink">DB_ENV->set_errpfx()</a> and <a href="../api_reference/C/envset_verbose.html" class="olink">DB_ENV->set_verbose()</a>.</p> - <p>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.</p> - <p>In addition, there are three methods to assist applications in -displaying their own error messages: <a href="../api_reference/C/envstrerror.html" class="olink">db_strerror()</a>, <a href="../api_reference/C/enverr.html" class="olink">DB_ENV->err()</a>, -and <code class="methodname">DB_ENV->errx()</code>. 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 <a href="../api_reference/C/enverr.html" class="olink">DB_ENV->err()</a> and -<code class="methodname">DB_ENV->errx()</code> methods use the error message configuration options -described previously to format and display error messages to appropriate -output devices.</p> + <p> + Normally, when an error occurs in the Berkeley DB library, + an integer value (either a Berkeley DB specific value or a + system <code class="literal">errno</code> 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. + </p> + <p> + 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: <a href="../api_reference/C/envset_errcall.html" class="olink">DB_ENV->set_errcall()</a>, + <a href="../api_reference/C/envset_errfile.html" class="olink">DB_ENV->set_errfile()</a>, <a href="../api_reference/C/envset_errpfx.html" class="olink">DB_ENV->set_errpfx()</a> and <a href="../api_reference/C/envset_verbose.html" class="olink">DB_ENV->set_verbose()</a>. + </p> + <p> + 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. + </p> + <p> + In addition, there are three methods to assist applications + in displaying their own error messages: <a href="../api_reference/C/envstrerror.html" class="olink">db_strerror()</a>, + <a href="../api_reference/C/enverr.html" class="olink">DB_ENV->err()</a>, and <code class="methodname">DB_ENV->errx()</code>. 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 <a href="../api_reference/C/enverr.html" class="olink">DB_ENV->err()</a> and + <code class="methodname">DB_ENV->errx()</code> methods use the + error message configuration options described previously to + format and display error messages to appropriate output + devices. + </p> </div> <div class="navfooter"> <hr /> |