Error is not written to error output

[jinek]

If exception happened while executing gpr it is caught by the catch which just returns code 1

gpr/src/GprTool/Program.cs

Line 58 in 274aa3b

catch (Exception e)

My question is why this catch is needed at all, because runtime aready returns non-zero code by itself, additionally the default handler will write error to error stream and other things, like suggestion to attach the debugger.
Can't we just simply remove it? Does it give any benefits?