------- Additional Comments From igodard at pacbell dot net 2004-11-24 00:02
-------
But it's your own message after the OS kills you, so I'd suggest saying:
"The compilation was killed by the OS, possibly due to an internal error or
possibly from running out of system resources such as memory. We suggest that
you first fix any reported errors. If the problem persists then try running
with
more swap space allocated or on a larger machine. If the problem still persists
then please file a bug report, see ..."
Not only will this get you fewer reports, it might also cause the compiler to
get badmouthed less often in the community by those who go back to VisualC++
rather than filing a report.
Ivan
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|WONTFIX |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18639
