Date: Fri, 14 May 2010 02:44:07 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Kostik Belousov <kostikbel@gmail.com> Cc: alc@freebsd.org, attilio@freebsd.org, freebsd-current@freebsd.org Subject: Re: kgdb unuseable with cores on current (for some people) Message-ID: <alpine.GSO.1.10.1005140243030.29136@multics.mit.edu> In-Reply-To: <20100514053907.GL83316@deviant.kiev.zoral.com.ua> References: <alpine.GSO.1.10.1005140013260.29136@multics.mit.edu> <20100514053907.GL83316@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 May 2010, Kostik Belousov wrote: > On Fri, May 14, 2010 at 12:55:35AM -0400, Benjamin Kaduk wrote: >> Hi all, >> >> As was revealed in a recent thread here [1], several people have been >> unable to use kgdb on coredumps for the past few months (but possibly not >> everyone). >> >> I am one of those affected, and have narrowed the breakage with a binary >> search to between SVN revisions 202883 and 202954 (that is, Jan 23 1200h >> and Jan 25 0000h). Looking at the changes, alc's revision 202897 and >> attilio's revision 202933 look to be the most plausible culprits in terms >> of what they touched. I will continue with my bisection, but with only 36 >> revisions in play, it is probably worth looking for the bug in parallel >> with the bisection. > > Try reverting r202897 on fresh HEAD. I very much doubt that r202933 > can be responsible. > Indeed, 202933 was cleared of blame in the latest bisection. I'm currently pulling up to HEAD and will try reverting 202897. -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1005140243030.29136>