Date: Fri, 1 Apr 2016 00:45:19 -0400 From: J David <j.david.lists@gmail.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Catching core files in read-only jails Message-ID: <CABXB=RTHetL-mjehjSaTVT2ipLTQySE2Y8UCUQXcM7_hWV3g_Q@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
If an application is running on a production server in a read-only jail for security purposes, and it crashes occasionally due to some unknown bug, is there any way to catch a core file? Setting kern.corefile seems to still be relative to the jail. (Or, at least, no corefile is generated.) There are a lot of these processes and they don’t crash very often, so leaving gdb attached isn’t really feasible either. (It’s been tried, but apparently requires a bit more luck than is currently in evidence.) Thusfar all attempts to get it to crash in a controlled/test environment have also been unsuccessful. Does anyone have any ideas for how to find out what’s causing the crash? Thanks for any advice!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABXB=RTHetL-mjehjSaTVT2ipLTQySE2Y8UCUQXcM7_hWV3g_Q>