Date: Tue, 4 Aug 2015 11:36:11 +0800 From: Julian Elischer <julian@freebsd.org> To: Marcel Moolenaar <marcel@xcllnt.net>, Eric Badger <eric_badger@dell.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Marcel Moolenaar <marcel@FreeBSD.org> Subject: Re: Appending to message buffer while in ddb Message-ID: <55C0332B.5090700@freebsd.org> In-Reply-To: <16785483-7FD3-4475-9958-168528AFB2D9@xcllnt.net> References: <55BFC80B.2000005@dell.com> <16785483-7FD3-4475-9958-168528AFB2D9@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/4/15 4:21 AM, Marcel Moolenaar wrote: >> On Aug 3, 2015, at 12:59 PM, Eric Badger <eric_badger@dell.com> wrote: >> >> Hi there, >> >> Since r226435, output from kernel printf/log functions is not appended to the message buffer when in ddb. The commit message doesn't call this out specifically; instead it appears to have been to address double printing to the console while in ddb. I noticed this because a ddb script which previously resulted in some things ending up in a textdump's msgbuf.txt no longer does so. It may be that the answer is "use db_printf in ddb", which is ok, but I thought I'd check anyway to see if the aforementioned change was indeed intentional, since I wasn't able to dig up any discussion about it. > It’s a direct consequence. and really annoying > > -- > Marcel Moolenaar > marcel@xcllnt.net >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55C0332B.5090700>