Date: Sun, 18 Apr 2021 13:18:00 -0600 From: Ian Lepore <ian@freebsd.org> To: Lucas Nali de =?ISO-8859-1?Q?Magalh=E3es?= <rollingbits@gmail.com>, freebsd-hackers@freebsd.org Subject: Re: Debugging signal 11 Message-ID: <9d3b5c0cc7051f410fd04ff9ffba8aa0b5b32167.camel@freebsd.org> In-Reply-To: <4AF3D639-FB07-46B5-9058-114576BD4EDB@gmail.com> References: <s5d7t6$bdl$1@ciao.gmane.io> <4AF3D639-FB07-46B5-9058-114576BD4EDB@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2021-04-18 at 15:53 -0300, Lucas Nali de Magalhães wrote: > This also isn't the usual. Debugging a running process is possible but > the process you used is the wrong one. Debugging init, OTOH, is a > completely different story: init is the first process and is the most > important process of any unix. The actual command varies from > debugger to debugger but in gdb, "attach pid" may do the trick for > you. You will need to be extra cautious because of you are aiming init. > Ideally, init is the process supposed to catch the signals and keep > the system running. So a break into it may cause your system to crash. Given that it is init that is segfaulting, how to you propose that the OP lauch gdb in order to do an attach to init? In other words: there is a reason the OP is trying to use the kernel debugger to examine what's going on here. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9d3b5c0cc7051f410fd04ff9ffba8aa0b5b32167.camel>