Date: Mon, 22 Feb 2016 12:32:45 +0200 From: Tommi Pernila <tommi.pernila@iki.fi> To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= <jean-sebastien.pedron@dumbbell.fr> Cc: freebsd-x11@freebsd.org Subject: Re: Guide to contribute to kernel video drivers Message-ID: <CABHD1wSFdGUZ5wmDzN8Twu5F1BeERoJZ5zeRaGjNMv%2Bbb7gwYA@mail.gmail.com> In-Reply-To: <56C8F89D.5060703@dumbbell.fr> References: <56C708E9.8050203@FreeBSD.org> <20160220104349.2bc8b22a@fujitsu> <56C8F89D.5060703@dumbbell.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Sun, Feb 21, 2016 at 1:37 AM, Jean-S=C3=A9bastien P=C3=A9dron < jean-sebastien.pedron@dumbbell.fr> wrote: > Le 20/02/2016 08:43, Eax Melanhovich a =C3=A9crit : > > Hello > > Hi! > > > Thanks a lot for a guide! > > You're welcome! > > Similarly many thanks to Jean for the guide. > > Do I right understand that the only way to debug a kernel is to crash > > it and then analyze a dump using gdb? Is it possible to attach to a > > running kernel remotely? > > It's probably possible to debug a live kernel, but I never did this > because I don't have a working serial remote access. > > Wouldn't this be possible over ssh? -T
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABHD1wSFdGUZ5wmDzN8Twu5F1BeERoJZ5zeRaGjNMv%2Bbb7gwYA>