Hello,
thanks for reporting this; this is a bug, but not a security issue: stdout behaves differently in interactive and noninteractive mode; unfortunately we _exit() instead of exit() after printing the information so atexit is not called and stdout is not flushed.
We will have to fix this.
Kind regards,
Ondrej Kolacek