Appending to message buffer while in ddb

[Julian Elischer]

On 8/4/15 11:36 AM, Julian Elischer wrote:
> On 8/4/15 4:21 AM, Marcel Moolenaar wrote:
>>> On Aug 3, 2015, at 12:59 PM, Eric Badger <eric_badger at 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

though I can understand not wanting to have one's message buffer 
flushed out with new stuff from ddb.
>>
>> -- 
>> Marcel Moolenaar
>> marcel at xcllnt.net
>>
>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe at freebsd.org"
>
>