Date: Fri, 29 Jan 2016 19:15:29 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-7sNut95Imi@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 #17 from rblayzor@inoc.net --- I'm not claiming that the bug here that I've reported does not exist in 10.= 0 or 10.1, I'm just saying that we've seen this bug during our entire release cy= cle of 10.1. (which was almost a good year). We only started noticing this issue with process seg faults after updating = to 10.2. We were running the same versions of Dovecot and Exim on 10.1 when we started noticing it in 10.2. That's when we force rebuilt all of the binari= es under 10.2 to no avail. Dovecot and Exim are NOT the only processes that we've seen core out, they = are just the processes we see the most often. I've seen cron do it, ntpd and so= me other port binaries. I remember looking at their core files and seeing the = same "cannot access memory" errors in the backtrace. It was only then I started paying attention more and have been gathering more and more debug informati= on on this strange issue. --=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-7sNut95Imi>