The indexes returned by ***_get_ex_new_index() functions are used when

setting stack (actually, array) values in ex_data. So only increment the
global counters if the underlying CRYPTO_get_ex_new_index() call succeeds.
This change doesn't make "ex_data" right (see the comment at the head of
ex_data.c to know why), but at least makes the source code marginally less
frustrating.
This commit is contained in:
Geoff Thorpe
2001-08-12 16:52:00 +00:00
parent f0446ca8d7
commit b7727ee616
9 changed files with 40 additions and 32 deletions

View File

@@ -222,9 +222,10 @@ void DH_free(DH *r)
int DH_get_ex_new_index(long argl, void *argp, CRYPTO_EX_new *new_func,
CRYPTO_EX_dup *dup_func, CRYPTO_EX_free *free_func)
{
dh_meth_num++;
return(CRYPTO_get_ex_new_index(dh_meth_num-1,
&dh_meth,argl,argp,new_func,dup_func,free_func));
if(CRYPTO_get_ex_new_index(dh_meth_num, &dh_meth, argl, argp,
new_func, dup_func, free_func) < 0)
return -1;
return (dh_meth_num++);
}
int DH_set_ex_data(DH *d, int idx, void *arg)