Date: Fri, 23 Jun 2006 17:32:00 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Giorgos Keramidas <keramida@freebsd.org> Cc: freebsd-doc@freebsd.org Subject: Re: [patch] deadlock debugging Message-ID: <20060623143200.GJ5115@deviant.kiev.zoral.com.ua> In-Reply-To: <20060623141756.GA9283@gothmog.pc> References: <20060607084346.GA21391@deviant.kiev.zoral.com.ua> <20060623132558.GD7062@gothmog.pc> <20060623135837.GI5115@deviant.kiev.zoral.com.ua> <20060623141756.GA9283@gothmog.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
--6TC23+W66xmFESAX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 23, 2006 at 05:17:56PM +0300, Giorgos Keramidas wrote: > On 2006-06-23 16:58, Kostik Belousov <kostikbel@gmail.com> wrote: > > My intent for the addition was to have the place for pointing out when > > asked "how to debug deadlocks" ? Could you additions and my do-it > > guide coexist side-by-side ? For instance, by summarizing the > > information developers want to obtain from the problem machine, at the > > end of section ? >=20 > That's a good idea. Do you think it makes sense to split the addition > to sub-sections, i.e.: >=20 > + Debugging Kernel Deadlocks > - What is a deadlock > - Using DDB to gather deadlock information > - Kernel options useful for deadlock debugging > - Summary >=20 > I didn't add <sect2> elements around the text I sent, but this shouldn't > be very hard to do, I guess. Exactly! This structuring going to be the best. --6TC23+W66xmFESAX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEm/tfC3+MBN1Mb4gRAqJhAJ9AKpn33Xx/9pqr0ocW3qA20pItxACgu1S2 N8TI6u8HlE0vxblC+dzb96U= =Du9n -----END PGP SIGNATURE----- --6TC23+W66xmFESAX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060623143200.GJ5115>