Date: Fri, 14 May 2010 08:39:07 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: alc@freebsd.org, attilio@freebsd.org, freebsd-current@freebsd.org Subject: Re: kgdb unuseable with cores on current (for some people) Message-ID: <20100514053907.GL83316@deviant.kiev.zoral.com.ua> In-Reply-To: <alpine.GSO.1.10.1005140013260.29136@multics.mit.edu> References: <alpine.GSO.1.10.1005140013260.29136@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--SUaMdvPJwViBZG9r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 14, 2010 at 12:55:35AM -0400, Benjamin Kaduk wrote: > Hi all, >=20 > As was revealed in a recent thread here [1], several people have been=20 > unable to use kgdb on coredumps for the past few months (but possibly not= =20 > everyone). >=20 > I am one of those affected, and have narrowed the breakage with a binary= =20 > search to between SVN revisions 202883 and 202954 (that is, Jan 23 1200h= =20 > and Jan 25 0000h). Looking at the changes, alc's revision 202897 and=20 > attilio's revision 202933 look to be the most plausible culprits in terms= =20 > of what they touched. I will continue with my bisection, but with only 3= 6=20 > revisions in play, it is probably worth looking for the bug in parallel= =20 > with the bisection. Try reverting r202897 on fresh HEAD. I very much doubt that r202933 can be responsible. --SUaMdvPJwViBZG9r Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkvs4fsACgkQC3+MBN1Mb4iLrACcDLaRSwh4WkBb4khXHXVDn85S pDYAoLbk7/vt5t+a+wAukXOKRP2jvl0T =g73c -----END PGP SIGNATURE----- --SUaMdvPJwViBZG9r--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100514053907.GL83316>