Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Aug 2017 12:07:43 -0700
From:      Kirk McKusick <mckusick@mckusick.com>
To:        Aijaz Baig <aijazbaig1@gmail.com>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: Tips on remote debugging for filesystem code
Message-ID:  <201708271907.v7RJ7h18017535@chez.mckusick.com>
In-Reply-To: <CAHB2L%2BcrbMGvwAB7zx%2BnaLC5DTbOy7RWbxyFyPCGAZmaLoQ5fg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> From: Aijaz Baig <aijazbaig1@gmail.com>
> Date: Sun, 27 Aug 2017 22:04:41 +0530
> Subject: Re: Tips on remote debugging for filesystem code
> To: Kirk McKusick <mckusick@mckusick.com>
> =

> Thanks for the heads up Kirk. Unfortunately I just ran into a roadblock
> with Bhyve since I am running FreeBSD on core2duo which "officially"
> doesn't support Bhyve yet.
> =

> Is there some other way I can get this to work? I have installed FreeBSD
> bare metal now if it helps.

Best solution is to get some hardware that can run bhyve :-)

Absent that, you can revert to the historic method of remote
debugging over serial lines, see chapter 10 of the FreeBSD
handbook. More specifically:

https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-onlin=
e-gdb.html

	Kirk McKusick



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201708271907.v7RJ7h18017535>