Date: Fri, 18 Mar 2016 23:35:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-9cg5PrvJeE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204426-16@https.bugs.freebsd.org/bugzilla/> References: <bug-204426-16@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #67 from John Baldwin <jhb@FreeBSD.org> --- Sorry for another possible hail mary, but I've noticed that many of your fa= ults are in the thread library. There were several changes to libthr between 10= .1 and 10.2. They should all be bug fixes (in particular fixes to allow applications to dlopen() an object that uses libthr). If these changes to libthr are relevant then there are a few things to investigate and/or try: 1) Can you run ldd on your dovecot and exim binaries to see if they are directly linked against libthr? 2) Do you know if your binaries are loading any "plugins" (e.g. SASL auth mechanisms, milters (I know postfix and sendmail can both use milters for things like greylisting, etc.))? If you are, are any of your plugins linked against libthr? If the answer to 1) is no, then the first thing to possibly try is to set LD_PRELOAD=3Dlibthr.so.3 in the environment of the dovecot and exim binarie= s when you start them up. (If using rc.d scripts you can do this via foo_env variables in rc.conf.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204426-16-9cg5PrvJeE>