Date: Mon, 01 Feb 2016 12:51:32 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-BjSDdE7Cud@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204426-16@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204426 --- Comment #22 from rblayzor@inoc.net --- When I see processes core dump along with the line message 'Failed to write core file for process XXX (error 14)", that is generally where I will see an incomplete core file with a "cannot access memory". So that may be related to the bug you mentioned. I do get occasional good core dumps, as noted above. At this time I cannot run stable to patch the core dump issue. I did however install clang3.6. I have rebuilt the ports we are seeing problems with against that just to rule it out. That is however, very unlikely. I will continue to gather more dumps if they produce valid cores. If there is a patch I can rebuild against that fixes the "error 14" issue, I'll give is a whirl. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204426-16-BjSDdE7Cud>