Date: Thu, 03 Dec 2015 11:33:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-T9yliX1KyH@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=204426 --- Comment #4 from rblayzor@inoc.net --- Still seeing programs (various) randomly crash with "cannot access memory" type core dumps. As previously mentioned, we never experienced this on 10.1-RELEASE. Only after upgrading VM"s to 10.2 did we start noticing this.. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `exim'. Program terminated with signal 11, Segmentation fault. #0 0x00000000004b9f6b in store_reset_3 (ptr=Cannot access memory at address 0x7fffffffc838 ) at store.c:360 360 store.c: No such file or directory. in store.c (gdb) -- 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-T9yliX1KyH>