summaryrefslogtreecommitdiff
path: root/docs/installation/debug.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/installation/debug.html')
-rw-r--r--docs/installation/debug.html130
1 files changed, 64 insertions, 66 deletions
diff --git a/docs/installation/debug.html b/docs/installation/debug.html
index a91b70e3..fba56d02 100644
--- a/docs/installation/debug.html
+++ b/docs/installation/debug.html
@@ -14,13 +14,11 @@
<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>
- <th colspan="3" align="center">Chapter 3. 
- Debugging Applications
- </th>
+ <th colspan="3" align="center">Chapter 3.  Debugging Applications </th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="install_multiple.html">Prev</a> </td>
@@ -34,9 +32,7 @@
<div class="titlepage">
<div>
<div>
- <h2 class="title"><a id="debug"></a>Chapter 3. 
- Debugging Applications
- </h2>
+ <h2 class="title"><a id="debug"></a>Chapter 3.  Debugging Applications </h2>
</div>
</div>
</div>
@@ -69,32 +65,32 @@
<dl>
<dt>
<span class="sect2">
- <a href="debug_printlog.html#idm1304224">Augmenting the Log for Debugging</a>
+ <a href="debug_printlog.html#idp164880">Augmenting the Log for Debugging</a>
</span>
</dt>
<dt>
<span class="sect2">
- <a href="debug_printlog.html#idm1194048">Extracting Committed Transactions and Transaction Status</a>
+ <a href="debug_printlog.html#idp136104">Extracting Committed Transactions and Transaction Status</a>
</span>
</dt>
<dt>
<span class="sect2">
- <a href="debug_printlog.html#idm1341784">Extracting Transaction Histories</a>
+ <a href="debug_printlog.html#idp166064">Extracting Transaction Histories</a>
</span>
</dt>
<dt>
<span class="sect2">
- <a href="debug_printlog.html#idm986800">Extracting File Histories</a>
+ <a href="debug_printlog.html#idp171384">Extracting File Histories</a>
</span>
</dt>
<dt>
<span class="sect2">
- <a href="debug_printlog.html#idm1437640">Extracting Page Histories</a>
+ <a href="debug_printlog.html#idp183288">Extracting Page Histories</a>
</span>
</dt>
<dt>
<span class="sect2">
- <a href="debug_printlog.html#idm680600">Other log processing tools</a>
+ <a href="debug_printlog.html#idp184088">Other log processing tools</a>
</span>
</dt>
</dl>
@@ -109,87 +105,89 @@
</div>
</div>
</div>
+ <p>
+ Because Berkeley DB is an embedded library, debugging
+ applications that use Berkeley DB is both harder and easier
+ than debugging a separate server. Debugging can be harder
+ because when a problem arises, it is not always readily
+ apparent whether the problem is in the application, is in the
+ database library, or is a result of an unexpected interaction
+ between the two. Debugging can be easier because it is easier
+ to track down a problem when you can review a stack trace
+ rather than deciphering interprocess communication messages.
+ This chapter is intended to assist you with debugging
+ applications and reporting bugs to us so that we can provide
+ you with the correct answer or fix as quickly as possible.
+ </p>
<p>
- Because Berkeley DB is an embedded library, debugging applications that
- use Berkeley DB is both harder and easier than debugging a separate
- server. Debugging can be harder because when a problem arises, it is
- not always readily apparent whether the problem is in the application,
- is in the database library, or is a result of an unexpected interaction
- between the two. Debugging can be easier because it is easier to track
- down a problem when you can review a stack trace rather than
- deciphering interprocess communication messages. This chapter is
- intended to assist you with debugging applications and reporting bugs
- to us so that we can provide you with the correct answer or fix as
- quickly as possible.
-</p>
- <p>
- When you encounter a problem, there are a few general actions you can
- take:
-</p>
+ When you encounter a problem, there are a few general
+ actions you can take:
+ </p>
<div class="variablelist">
<dl>
<dt>
<span class="term">Review the Berkeley DB error output:</span>
</dt>
<dd>
- <p>
- If an error output mechanism has been configured in the
- Berkeley DB environment, additional run-time error messages
- are made available to the applications. If you are not
- using an environment, it is well worth modifying your
- application to create one so that you can get more detailed
- error messages. See
- <a class="xref" href="debug_runtime.html" title="Run-time error information">Run-time error information</a>
- for more information on configuring Berkeley DB to output these
- error messages.
- </p>
+ <p>
+ If an error output mechanism has been
+ configured in the Berkeley DB environment,
+ additional run-time error messages are made
+ available to the applications. If you are not
+ using an environment, it is well worth modifying
+ your application to create one so that you can get
+ more detailed error messages. See <a class="xref" href="debug_runtime.html" title="Run-time error information">Run-time error information</a> for more
+ information on configuring Berkeley DB to output
+ these error messages.
+ </p>
</dd>
<dt>
- <span class="term">Review the options available for the <a href="../api_reference/C/envset_verbose.html" class="olink">DB_ENV-&gt;set_verbose()</a> method:</span>
+ <span class="term">Review the options available for the
+ <a href="../api_reference/C/envset_verbose.html" class="olink">DB_ENV-&gt;set_verbose()</a> method:</span>
</dt>
<dd>
<p>
- Look to see if it offers any additional informational
- and/or debugging messages that might help you understand
- the problem.
- </p>
+ Look to see if it offers any additional
+ informational and/or debugging messages that might
+ help you understand the problem.
+ </p>
</dd>
<dt>
<span class="term">Add run-time diagnostics:</span>
</dt>
<dd>
- <p>
- You can configure and build Berkeley DB to perform run-time
- diagnostics. (By default, these checks are not done
- because they can seriously impact performance.) See
- <a class="xref" href="debug_compile.html" title="Compile-time configuration">Compile-time configuration</a>
- for more information.
- </p>
+ <p>
+ You can configure and build Berkeley DB to
+ perform run-time diagnostics. (By default, these
+ checks are not done because they can seriously
+ impact performance.) See <a class="xref" href="debug_compile.html" title="Compile-time configuration">Compile-time configuration</a> for more
+ information.
+ </p>
</dd>
<dt>
<span class="term">Apply all available patches:</span>
</dt>
<dd>
<p>
- Before reporting a problem in Berkeley DB, please upgrade
- to the latest Berkeley DB release, if possible, or at least
- make sure you have applied any updates available for your
- release from the
- <a class="ulink" href="http://www.oracle.com/technetwork/database/berkeleydb/downloads/index.html" target="_top">
- Berkeley DB web site
- </a>.
- </p>
+ Before reporting a problem in Berkeley DB,
+ please upgrade to the latest Berkeley DB release,
+ if possible, or at least make sure you have
+ applied any updates available for your release
+ from the <a class="ulink" href="http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index.html" target="_top">
+ Berkeley DB web site </a>.
+ </p>
</dd>
<dt>
<span class="term">Run the test suite:</span>
</dt>
<dd>
- <p>
- If you see repeated failures or failures of simple test
- cases, run the Berkeley DB test suite to determine whether
- the distribution of Berkeley DB you are using was built and
- configured correctly.
- </p>
+ <p>
+ If you see repeated failures or failures of
+ simple test cases, run the Berkeley DB test suite
+ to determine whether the distribution of Berkeley
+ DB you are using was built and configured
+ correctly.
+ </p>
</dd>
</dl>
</div>