New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rm err get string table #1389
Rm err get string table #1389
Conversation
See #1379 |
hash = get_hash(0, 0); | ||
if (hash) | ||
p = lh_ERR_STRING_DATA_retrieve(hash, d); | ||
if (int_error_hash) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!= NULL?
I'm happy to see this in preference to 1379, modulo style nits. |
yeah, fixed those with an updated commit. thanks. |
@@ -1800,7 +1800,6 @@ EVP_PKEY_meth_get_verify_recover 1785 1_1_0 EXIST::FUNCTION: | |||
NAME_CONSTRAINTS_check 1786 1_1_0 EXIST::FUNCTION: | |||
X509_CERT_AUX_it 1787 1_1_0 EXIST:!EXPORT_VAR_AS_FUNCTION:VARIABLE: | |||
X509_CERT_AUX_it 1787 1_1_0 EXIST:EXPORT_VAR_AS_FUNCTION:FUNCTION: | |||
ERR_get_string_table 1788 1_1_0 EXIST::FUNCTION: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This introduces a "gap" in libcrypto.num. Do we need to recreate this before final release? Not a problem for this MR though I think.
+1 for merge after beta |
Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #1389)
Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #1389)
merged, thanks. |
No description provided.