catching Errors in OS callbacks how to print stack trace?

[Adam D. Ruppe]

On Monday, 24 February 2020 at 13:42:01 UTC, NaN wrote:
>         try { writeln(e.msg); }

try `writeln(e.toString());` instead.

msg only contains the message passed to the constructor by 
itself, toString includes the file/line and stack trace members 
too.

easiest way usually.