So thanks to all of you,
adding the following dpatch as indicated by Eric resolves the SEGFAULT
and I can resume troubleshooting my configuration issues :(
ad...@valhalla:~/packages/cyrus-sasl2$ cat 0021_fix_sasl_mutex.dpatch
----8<-------------
#! /bin/sh /usr/share/dpatch/dpatch-run
## 0021_fix_sasl_mutex.dpatch by <ad...@valhalla.mgr>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Fix SEGFAULT on sasl_mutex. Debian Bug #405495
@DPATCH@
--- trunk~/lib/common.c 2009-01-05 12:20:53.000000000 +0100
+++ trunk/lib/common.c 2009-01-05 12:24:19.000000000 +0100
@@ -150,9 +150,17 @@
&sasl_mutex_free
};
-void sasl_set_mutex(sasl_mutex_alloc_t *n, sasl_mutex_lock_t *l,
- sasl_mutex_unlock_t *u, sasl_mutex_free_t *d)
-{
+void sasl_set_mutex(sasl_mutex_alloc_t *n,
+ sasl_mutex_lock_t *l,
+ sasl_mutex_unlock_t *u,
+ sasl_mutex_free_t *d)
+{
+ /* Disallow mutex function changes once sasl_client_init
+ and/or sasl_server_init is called */
+ if(_sasl_server_cleanup_hook || _sasl_client_cleanup_hook){
+ return;
+ }
+
_sasl_mutex_utils.alloc=n;
_sasl_mutex_utils.lock=l;
_sasl_mutex_utils.unlock=u;
----8<-------------
Regards,
- lars.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
