Date: Sun, 30 Jul 2006 15:42:15 +0200 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: "Only OpenSource" <onlyopensource@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: how to panic FreeBSD Message-ID: <20060730154215.42a9ca28@localhost> In-Reply-To: <a779d4420607292320l14a41c80t5eee4694bfab99e3@mail.gmail.com> References: <a779d4420607292320l14a41c80t5eee4694bfab99e3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_dNVeLIaCGZqa/CkANZ=8hn. Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Only OpenSource" <onlyopensource@gmail.com> wrote: > I am trying to learn kernel debugging and one of the approaches I > have come up with is to introduce situations in the sys code by which > the compiled kernel is buggy > and will panic. >=20 > My query is what are the typical bugs that I can introduce in say by > which the kernel > would panic. If you browse the filed problem reports, you will find more than enough real panics and if you also have a look at the closed ones, you'll find solutions as well. You could also panic your systems with classics like: - kldloading /dev/mem - kldloading kernel modules that aren't in sync with the kernel - mounting a file system through USB and then unplugging the drive without umounting first=20 Fabian --=20 http://www.fabiankeil.de/ --Sig_dNVeLIaCGZqa/CkANZ=8hn. Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEzLdOjV8GA4rMKUQRAhfoAJ96t7u/SR6iL2JrZGNC5vEx35Ix5QCgiRft 1zcrBvi7ldtCzNK6VLtFfLc= =CX2p -----END PGP SIGNATURE----- --Sig_dNVeLIaCGZqa/CkANZ=8hn.--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060730154215.42a9ca28>