From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/installation/debug.html | 130 +++++++++++++++++++++---------------------- 1 file changed, 64 insertions(+), 66 deletions(-) (limited to 'docs/installation/debug.html') 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 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

- + @@ -34,9 +32,7 @@
-

Chapter 3.  - Debugging Applications -

+

Chapter 3.  Debugging Applications

@@ -69,32 +65,32 @@
- Augmenting the Log for Debugging + Augmenting the Log for Debugging
- Extracting Committed Transactions and Transaction Status + Extracting Committed Transactions and Transaction Status
- Extracting Transaction Histories + Extracting Transaction Histories
- Extracting File Histories + Extracting File Histories
- Extracting Page Histories + Extracting Page Histories
- Other log processing tools + Other log processing tools
@@ -109,87 +105,89 @@ +

+ 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. +

- 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: -

+ 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. -

+

+ 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 the options available for the DB_ENV->set_verbose() method: + Review the options available for the + DB_ENV->set_verbose() method:

- Look to see if it offers any additional informational - and/or debugging messages that might help you understand - the problem. -

+ Look to see if it offers any additional + informational and/or debugging messages that might + help you 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. -

+

+ 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 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 - - Berkeley DB web site - . -

+ 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 + Berkeley DB 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. -

+

+ 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. +

-- cgit v1.2.1
Chapter 3.  - Debugging Applications - Chapter 3.  Debugging Applications
Prev