wxSQLite3CipherSQLCipher : InitializeFromGlobalDefault crash

[MAJOR-KENIX]

Vor allem möchte ich mich bei dir für deine Arbeit bedanken.

wxSQLite3CipherSQLCipher && wxSQLite3CipherRC4 && wxSQLite3CipherChaCha20 && wxSQLite3CipherAes256 && wxSQLite3CipherAes128 InitializeFromGlobalDefault crash.

That crash
wxSQLite3CipherAes256 *b = new wxSQLite3CipherAes256(); b->InitializeFromGlobalDefault();

That work
wxSQLite3Cipher *a = new wxSQLite3Cipher(); a->InitializeFromGlobalDefault()

[utelle]

Vor allem möchte ich mich bei dir für deine Arbeit bedanken.

You are welcome.

wxSQLite3CipherSQLCipher && wxSQLite3CipherRC4 && wxSQLite3CipherChaCha20 && wxSQLite3CipherAes256 && wxSQLite3CipherAes128 InitializeFromGlobalDefault crash.

That crash wxSQLite3CipherAes256 *b = new wxSQLite3CipherAes256(); b->InitializeFromGlobalDefault();

I can confirm that this call can crash. But only if the wxSQLite3 library was not initialized.

The problem can be avoided, by calling the static method wxSQLite3Database::InitializeSQLite() as early as possible after the application started. At least before calling InitializeFromGlobalDefault().

Nevertheless, thanks for reporting the issue. A crash should never happen, even if initialization hasn't been called. I will modify the underlying implementation in SQLite3 Multiple Ciphers. This may take a couple of days, but I will drop a note here, when the problem has been fixed.

That work wxSQLite3Cipher *a = new wxSQLite3Cipher(); a->InitializeFromGlobalDefault()

This is not surprising, because the method of the base class simply does nothing.

[MAJOR-KENIX]

Sie haben absolut recht, vielen Dank dafür.

[utelle]

Release 4.9.7 fixes the problem.