Date: Fri, 14 May 2010 15:15:21 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Alan Cox <alc@cs.rice.edu> Cc: Kostik Belousov <kostikbel@gmail.com>, alc@freebsd.org, freebsd-current@freebsd.org Subject: Re: kgdb unuseable with cores on current (for some people) Message-ID: <alpine.GSO.1.10.1005141514140.29136@multics.mit.edu> In-Reply-To: <alpine.GSO.1.10.1005141346170.29136@multics.mit.edu> References: <alpine.GSO.1.10.1005140013260.29136@multics.mit.edu> <20100514053907.GL83316@deviant.kiev.zoral.com.ua> <alpine.GSO.1.10.1005140243030.29136@multics.mit.edu> <4BED8ADE.1030100@cs.rice.edu> <alpine.GSO.1.10.1005141346170.29136@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 May 2010, Benjamin Kaduk wrote: > > Hm, but the "Cannot access memory" is preceeded by "Unread portion of the > kernel message buffer:\n"; I don't remember whether that was there before. > > I'll compile another kernel from stock HEAD to check if that's actually due > to the patch (or just poor memory on my part). The "Unread portion of the kernel message buffer:" text is new with Alan's patch. So, it seems to be a step in the right direction, but not a full fix. -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1005141514140.29136>