2
<!--Copyright 1997-2002 by Sleepycat Software, Inc.-->
3
<!--All rights reserved.-->
4
<!--See the file LICENSE for redistribution information.-->
7
<title>Berkeley DB Reference Guide: Introduction</title>
8
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
9
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
12
<a name="2"><!--meow--></a>
13
<table width="100%"><tr valign=top>
14
<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Debugging Applications</dl></h3></td>
15
<td align=right><a href="../../ref/install/rpm.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/debug/compile.html"><img src="../../images/next.gif" alt="Next"></a>
18
<h1 align=center>Introduction</h1>
19
<p>Because Berkeley DB is an embedded library, debugging applications that use
20
Berkeley DB is both harder and easier than debugging a separate server.
21
Debugging can be harder because when a problem arises, it is not always
22
readily apparent whether the problem is in the application, is in the
23
database library, or is a result of an unexpected interaction between
24
the two. Debugging can be easier because it is easier to track down a
25
problem when you can review a stack trace rather than deciphering
26
interprocess communication messages. This chapter is intended to assist
27
you with debugging applications and reporting bugs to us so that we can
28
provide you with the correct answer or fix as quickly as possible.
29
<p>When you encounter a problem, there are a few general actions you can
32
<p><dt>Review the Berkeley DB error output<dd>If an error output mechanism has been configured in the Berkeley DB
33
environment, additional run-time error messages are made available to
34
the applications. If you are not using an environment, it is well worth
35
modifying your application to create one so that you can get more
36
detailed error messages. See <a href="runtime.html">Run-time error
37
information</a> for more information on configuring Berkeley DB to output these
39
<p><dt>Review <a href="../../api_c/env_set_verbose.html">DB_ENV->set_verbose</a><dd>Check the list of flags for the <a href="../../api_c/env_set_verbose.html">DB_ENV->set_verbose</a> function, and
40
see if any of them will produce additional information that might help
41
understand the problem.
42
<p><dt>Add run-time diagnostics<dd>You can configure and build Berkeley DB to perform run-time diagnostics. (By
43
default, these checks are not done because they can seriously impact
44
performance.) See <a href="compile.html">Compile-time configuration</a> for more
46
<p><dt>Apply all available patches<dd>Before reporting a problem to Sleepycat Software, please upgrade to the
47
latest Sleepycat Software release of Berkeley DB, if possible, or at least
48
make sure you have applied any updates available for your release from
49
the <a href="http://www.sleepycat.com/update/index.html">Sleepycat
50
Software web site</a>.
51
<p><dt>Run the test suite<dd>If you see repeated failures or failures of simple test cases, run the
52
Berkeley DB test suite to determine whether the distribution of Berkeley DB you are
53
using was built and configured correctly.
55
<table width="100%"><tr><td><br></td><td align=right><a href="../../ref/install/rpm.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/debug/compile.html"><img src="../../images/next.gif" alt="Next"></a>
57
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>