🚀 go-pugleaf

    | Suggested message:
    | 
    | xgcc: Internal compiler error: program cc1 got fatal signal 4
    |       Please follow the instructions in the "Bugs" chapter of the GCC

In general, I think it is bad design to make individual programs
handle signals because the shell's standard message for a fatal signal
is not good enough.  It is bad because it is fixing special cases of a
general problem.  The right solution is to make the system and shell
print a better message all the time, containing whatever information
ought to be there.  It's not clean to change individual programs to
print their own messages to make up for this deficiency in the
system.

However, this idea of telling people to read the Bugs chapter might be
a good one.  I will think about it.