head 1.2;
access;
symbols
RPM_4_2_1:1.1.1.5
RPM_4_2:1.1.1.5
RPM_4_1_1:1.1.1.5
RPM_4_1:1.1.1.4
RPM_4_0_5:1.1.1.3
RPM_4_0_4:1.1.1.2
RPM_4_0_3:1.1.1.1
RPM:1.1.1;
locks; strict;
comment @# @;
1.2
date 2008.01.02.09.55.03; author rse; state dead;
branches;
next 1.1;
commitid z4cpSiAhOCXk5PLs;
1.1
date 2001.07.23.20.45.37; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2001.07.23.20.45.37; author rse; state Exp;
branches;
next 1.1.1.2;
1.1.1.2
date 2002.01.08.00.30.11; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.02; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.10.15.03.47.34; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.04.59; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB Reference Guide: Introduction
- Berkeley DB Reference Guide:
- Debugging Applications
|
  
|
Introduction
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.
When you encounter a problem, there are a few general actions you can
take:
- Review the Berkeley DB error output
- 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 Run-time error
information for more information on configuring Berkeley DB to output these
error messages.
- Review DB_ENV->set_verbose
- Check the list of flags for the DB_ENV->set_verbose function, and
see if any of them will produce additional information that might help
understand the problem.
- Add run-time diagnostics
- 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 Compile-time configuration for more
information.
- Apply all available patches
- Before reporting a problem to Sleepycat Software, please upgrade to the
latest Sleepycat Software release of Berkeley DB, if possible, or at least
make sure you have applied any updates available for your release from
the Sleepycat
Software web site.
- Run the test suite
- 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.
Copyright Sleepycat Software
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
a10 1
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d2 1
a2 1
a3 1
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d2 1
a2 1
d4 1
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d2 1
a2 1
a3 1
@