Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Apr 2021 13:37:50 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Ian Lepore <ian@freebsd.org>
Cc:        =?UTF-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= <rollingbits@gmail.com>,  FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: Debugging signal 11
Message-ID:  <CANCZdfrhsa5KTtZgSpoT%2BFacTWT-pAzQQJj49Uxf0mEFWKmLUg@mail.gmail.com>
In-Reply-To: <9d3b5c0cc7051f410fd04ff9ffba8aa0b5b32167.camel@freebsd.org>
References:  <s5d7t6$bdl$1@ciao.gmane.io> <4AF3D639-FB07-46B5-9058-114576BD4EDB@gmail.com> <9d3b5c0cc7051f410fd04ff9ffba8aa0b5b32167.camel@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 18, 2021, 1:18 PM Ian Lepore <ian@freebsd.org> wrote:

> On Sun, 2021-04-18 at 15:53 -0300, Lucas Nali de Magalh=C3=A3es 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.
>

Yea. I'm seeing this too on a new, lab machine. Not sure what is going on.
Since it's a new machine, I'm working through other, higher priority tasks
first. For me, it's only when I try a reboot -C that I see it... normal
reboot doesn't trigger it. And I don't see it on other models...

Warner

-- Ian
>
>
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org=
"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrhsa5KTtZgSpoT%2BFacTWT-pAzQQJj49Uxf0mEFWKmLUg>