The ABI has been broken in libmirage-3.0.5 by introducing the destroy_notify
parameter to mirage_context_set_password_function()
. However, the SONAME has not been updated. As a result, the necessity of application rebuild is hidden and the applications built against the old version are going to pretend everything is all right until they happen to attempt to run the destroy notify via unitialized value — which will hopefully result only in segv.
Indeed, this was an oversight on my part. It is now fixed in git, and will be sorted out in next release. Sorry for inconvenience and thanks for the report!
Cheers,
Rok