Date: Tue, 29 Mar 2016 12:00:17 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-73wx719OBo@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 #72 from Robert Blayzor <rblayzor@inoc.net> --- With the recent patches... I still get occasional unexpected crashes... Here is all I got on the last one.... Mar 29 05:26:18.617 mxs0.alb kernel: pid 97296 kpf 2 Mar 29 05:26:18.617 mxs0.alb kernel: pid 97296 kpf 2 Mar 29 05:26:18.617 mxs0.alb kernel: pid 97296 kpf 2 Mar 29 05:26:18.617 mxs0.alb kernel: pid 97296 kpf 2 Mar 29 05:26:18.825 mxs0.alb kernel: <4>Failed to write core file for proce= ss exim (error 14) Mar 29 05:26:18.825 mxs0.alb kernel: <6>pid 97296 (exim), uid 26: exited on signal 11 (gdb) bt full #0 __thr_fork () at /.amd_mnt/juno/pub/FreeBSD/10-STABLE/lib/libthr/thread/thr_fork.c:186 rtld_locks =3D Cannot access memory at address 0x7fffffffc7d0 Current language: auto; currently min So still looks like a libthr issue. I will see if I can grab a /lib/libthr.= so.3 from a FreeBSD 10.1 install I have locally and see if I still get these problems. --=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-73wx719OBo>