Running a large number of commands in KDL breaks KDL.

[kallisti5]

After running a large number of commands in kdl, you begin getting "out of memory for command execution" for every command.

kdebug> bfs_journal 
usage: bfs_journal <ptr-to-volume>
DebugAllocPool::Free(0xcce38028): bad address
DebugAllocPool::Free(0xcce38008): bad address
kdebug> v
  vars          vnode         vnode_caches  vnode_usage   vnodes      
kdebug> v
  vars          vnode         vnode_caches  vnode_usage   vnodes      
kdebug> pt
no completions
kdebug> pt
no completions
kdebug> ptr
no completions
kdebug> ptr
no completions
kdebug> cpu
out of memory for command executionkdebug>
kdebug> threads
out of memory for command executionkdebug> 
kdebug> thread
out of memory for command executionkdebug> 
kdebug> exit
out of memory for command executionkdebug> 
kdebug> continue
out of memory for command executionkdebug> 
kdebug> reboot
out of memory for command executionkdebug> 
kdebug> bfs_journal 
out of memory for command executionkdebug>

[kallisti5]

This could be actually due to another issue. Seeing odd disk io on virtio disk driver. Going to close this one as trash as it would be hard to troubleshoot.

[idefix]

One thing that can be fixed, is the missing newline after the "out of memory for command execution" message. See attached patch​.

(I didn't opt for the quick fix to add a newline after that message, as all exception messages with sExceptionPosition >= 0 don't have a newline.)

[idefix]

Patch to always add a newline after an exception message in KDL (untested).