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.52.53; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.08; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.55; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.08.00; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @
DB_ENV->set_alloc |
![]() ![]() |
#include <db.h>int DB_ENV->set_alloc(DB_ENV *db, void *(*app_malloc)(size_t size), void *(*app_realloc)(void *, size_t), void (*app_free)(void *));
Set the allocation functions used by the DB_ENV and DB methods to allocate or free memory owned by the application. The DB_ENV->set_alloc interface sets the allocation functions for a database environment; the DB->set_alloc interface sets the allocation functions for a single database. If both are specified, functions specified for a database will be used in preference to functions specified for environment.
There are a number of interfaces in Berkeley DB where memory is allocated by the library and then given to the application. For example, the DB_DBT_MALLOC flag, when specified in the DBT object, will cause the DB methods to allocate and reallocate memory which then becomes the responsibility of the calling application. (See DBT for more information.) Other examples are the Berkeley DB interfaces which return statistical information to the application: DB->stat, lock_stat, log_archive, log_stat, memp_stat, and txn_stat. There is one interface in the Berkeley DB where memory is allocated by the application and then given to the library: DB->associate.
On systems in which there may be multiple library versions of the standard allocation routines (notably Windows NT), transferring memory between the library and the application will fail because the Berkeley DB library allocates memory from a different heap than the application uses to free it. To avoid this problem, the DB_ENV->set_alloc and DB->set_alloc functions can be used to pass Berkeley DB references to the application's allocation routines.
It is not an error to not specify all three arguments to these interfaces; however, in that case the specified interfaces must be compatible with the standard library interfaces, as they will be used together. The functions specified must match the calling conventions of the ANSI C X3.159-1989 (ANSI C) library routines of the same name.
The DB_ENV->set_alloc interface may be used only to configure Berkeley DB before the DB_ENV->open interface is called.
The DB_ENV->set_alloc function returns a non-zero error value on failure and 0 on success.
The DB_ENV->set_alloc function may fail and return a non-zero error for the following conditions:
The DB_ENV->set_alloc function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_alloc function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
![]() ![]() |
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 d26 3 a28 3 void *(*app_malloc)(size_t size), void *(*app_realloc)(void *, size_t), void (*app_free)(void *)); d31 1 a31 1
Set the allocation functions used by the DB_ENV and DB d35 3 a37 1 allocation functions for a single database. d41 1 a41 1 will cause the DB methods to allocate and reallocate memory d45 2 a46 2 DB->stat, DB_ENV->lock_stat, DB_ENV->log_archive, DB_ENV->log_stat, DB_ENV->memp_stat, and DB_ENV->txn_stat. There is d56 5 a60 6
It is not an error to specify only one or two of the possible allocation function arguments to these interfaces; however, in that case the specified interfaces must be compatible with the standard library interfaces, as they will be used together. The functions specified must match the calling conventions of the ANSI C X3.159-1989 (ANSI C) library routines of the same name. a67 1
Called after DB_ENV->open was called. d87 2 d90 1 d93 1 d95 1 a95 1 DB_ENV->set_tas_spins, a96 1 DB_ENV->set_timeout, @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d26 1 a26 1 void *(*app_malloc)(size_t), d31 5 a35 2
Set the allocation functions used by the DB_ENV and DB methods to allocate or free memory owned by the application. d38 2 a39 2 DB_DBT_MALLOC flag, when specified in the DBT object, will cause the DB methods to allocate and reallocate memory d41 1 a41 1 DBT for more information.) Other examples are the Berkeley DB d52 1 a52 1 DB->set_alloc methods can be used to pass Berkeley DB references to the d60 3 a62 6
The DB_ENV->set_alloc method configures operations performed using the specified DB_ENV handle, not all operations performed on the underlying database environment.
The DB_ENV->set_alloc interface may not be called after the DB_ENV->open interface is called.
The DB_ENV->set_alloc method returns a non-zero error value on failure and 0 on success. d64 1 a64 1
The DB_ENV->set_alloc method may fail and return a non-zero error for the following conditions: d69 4 a72 6
The DB_ENV->set_alloc method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_alloc method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
Set the allocation functions used by the DB_ENV and DB methods to allocate or free memory owned by the application. The DB_ENV->set_alloc interface sets the allocation functions for a database environment; the DB->set_alloc interface sets the allocation functions for a single database. d36 2 a37 2 DB_DBT_MALLOC flag, when specified in the DBT object, will cause the DB methods to allocate and reallocate memory d39 1 a39 1 DBT for more information.) Other examples are the Berkeley DB d50 1 a50 1 DB->set_alloc functions can be used to pass Berkeley DB references to the d58 6 a63 3
The DB_ENV->set_alloc interface may be used only to configure Berkeley DB before the DB_ENV->open interface is called.
The DB_ENV->set_alloc function returns a non-zero error value on failure and 0 on success. d65 1 a65 1
The DB_ENV->set_alloc function may fail and return a non-zero error for the following conditions: d70 6 a75 4
The DB_ENV->set_alloc function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_alloc function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d77 1 a77 24 db_env_create, DB_ENV->close, DB_ENV->err, DB_ENV->errx DB_ENV->open, DB_ENV->remove, DB_ENV->set_alloc, DB_ENV->set_cachesize, DB_ENV->set_data_dir, DB_ENV->set_errcall, DB_ENV->set_errfile, DB_ENV->set_errpfx, DB_ENV->set_feedback, DB_ENV->set_flags, DB_ENV->set_paniccall, DB_ENV->set_recovery_init, DB_ENV->set_rpc_server, DB_ENV->set_shm_key, DB_ENV->set_tas_spins, DB_ENV->set_tmp_dir, DB_ENV->set_timeout, DB_ENV->set_verbose, db_strerror and db_version. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d26 1 a26 1 void *(*app_malloc)(size_t), d31 5 a35 2
Set the allocation functions used by the DB_ENV and DB methods to allocate or free memory owned by the application. d38 2 a39 2 DB_DBT_MALLOC flag, when specified in the DBT object, will cause the DB methods to allocate and reallocate memory d41 1 a41 1 DBT for more information.) Other examples are the Berkeley DB d52 1 a52 1 DB->set_alloc methods can be used to pass Berkeley DB references to the d60 3 a62 6
The DB_ENV->set_alloc method configures operations performed using the specified DB_ENV handle, not all operations performed on the underlying database environment.
The DB_ENV->set_alloc interface may not be called after the DB_ENV->open interface is called.
The DB_ENV->set_alloc method returns a non-zero error value on failure and 0 on success. d64 1 a64 1
The DB_ENV->set_alloc method may fail and return a non-zero error for the following conditions: d69 4 a72 6
The DB_ENV->set_alloc method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_alloc method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.