We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
在Sm3、Sm4Cbc传入long sm4_cbc_ctx、sm3_cbc_ctx时,Java应用程序崩溃,发生了SIGSEGV信号,访问了无效的内存地址:
The text was updated successfully, but these errors were encountered:
请问,在传输过程中,重新将Sm4对象反序列化后,sm4_cbc_ctx的数值跟传输前是一样的,但是会出现如下错误,请问怎么解决 41)
Sorry, something went wrong.
No branches or pull requests
在Sm3、Sm4Cbc传入long sm4_cbc_ctx、sm3_cbc_ctx时,Java应用程序崩溃,发生了SIGSEGV信号,访问了无效的内存地址:
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007ff5b9ec91b1, pid=31540, tid=0x00007ff5fe54f700
JRE version: OpenJDK Runtime Environment (8.0_392-b08) (build 1.8.0_392-b08)
Java VM: OpenJDK 64-Bit Server VM (25.392-b08 mixed mode linux-amd64 compressed oops)
Problematic frame:
C [libgmssl.so.3+0x2a1b1] sm4_cbc_encrypt_update+0x24
Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
The text was updated successfully, but these errors were encountered: