Date: Mon, 4 Jun 2018 13:21:40 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: Michael Schuster <michaelsprivate@gmail.com> Cc: freeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Unable to kill processes using either Ctrl-C or 'kill' Message-ID: <8286a5eb-9bc7-66a0-f84e-da49c12c1b07@ShaneWare.Biz> In-Reply-To: <CADqw_gLwsSKT3w8iyY7d9%2Bisqyt7YH4CvifRL2WG54OQdvK7Xw@mail.gmail.com> References: <9a7f62c4-80aa-7eea-91ec-6712612a0451@pobox.com> <CAOZUxFu7LkafvT30H_ZZG6uJ-CkU537RD=dSHcEP=UVRgOdrZw@mail.gmail.com> <CADqw_gLwsSKT3w8iyY7d9%2Bisqyt7YH4CvifRL2WG54OQdvK7Xw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/06/2018 04:33, Michael Schuster wrote: > most likely, being root or equivalent won't help in this case. If a > processes owner cannot kill it (using -9, which cannot be caught) that > implies that the process is hung in the kernel (signal delivery happens > when a process leaves kernel context). I this situation, is there any way to find what function the hung process is in? Attach and backtrace it? While I know I can attach lldb/gdb to a running process, I can't seem to find a way to interrupt a non-killable process to get control and see where it is or what it is doing. and... I just thought I should be looking at dtrace. -- FreeBSD - the place to B...Software Developing Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8286a5eb-9bc7-66a0-f84e-da49c12c1b07>