Please make sure that you don't use atexit() in a library. Also, while at it, please no exit() or abort(). Thanks! atexit() related issues are insanely troublesome to correct after the use has been introduced. Case point: github.com/openssl/openssl/iss… #development #coding #baddesign
3.0.12 broke pkcs11 engine · Issue #22508 · openssl/openssl
Hi, the testsuite for libp11-0.4.12 breaks in 3.0.12, works in 3.0.11. The testsuite: https://sources.debian.org/src/libp11/0.4.12-1/debian/tests/engine/ The segfault occurs while generating a cert...GitHub
Billy O'Neal
in reply to Harry Sintonen • • •daniel:// stenberg://
in reply to Billy O'Neal • • •Billy O'Neal
in reply to daniel:// stenberg:// • • •@bagder all assertion failures, stack protector, unhanded exception, etc.
It’s true that abort shouldn’t be called in normal operation but by definition it isn’t normal operation
daniel:// stenberg://
in reply to Billy O'Neal • • •Harry Sintonen
in reply to daniel:// stenberg:// • • •@bagder @malwareminigun C++ exceptions are generally a no-no, since they are not ABI stable.
Also, another thing I generally dislike is using setjmp / longjmp - that is just bad design. Some image decoding libraries seem to think this is a acceptable way doing error handling.
Billy O'Neal
in reply to daniel:// stenberg:// • • •Billy O'Neal
in reply to Billy O'Neal • • •daniel:// stenberg://
in reply to Billy O'Neal • • •Steve Downey
in reply to daniel:// stenberg:// • • •If applications could be trusted, asserts would never fire.
Billy O'Neal
in reply to daniel:// stenberg:// • • •