On 08/03/2015 03:21 PM, Marcel Moolenaar wrote:
On Aug 3, 2015, at 12:59 PM, Eric Badger 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 ha
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
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
On 8/4/15 4:21 AM, Marcel Moolenaar wrote:
On Aug 3, 2015, at 12:59 PM, Eric Badger 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 bee
> On Aug 3, 2015, at 12:59 PM, Eric Badger 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 t
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
scrip
