--- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-24
22:15 ---
But most of the time again any out of memory is usually a bug.
--
What|Removed |Added
--- Additional Comments From igodard at pacbell dot net 2004-11-24 22:12
---
Thank you for the excellent explanation, but your explanation was redundant; I
do (and did) understand why the nature of the problem is opaque. I'm not filing
this bug because I don't understand; I'm filing a
--- Additional Comments From bangerth at dealii dot org 2004-11-24 16:49
---
This has been discussed numerous times, and the main problem people had
in coming up with better diagnostics is that the operating system does
not communicate to a program why it is being killed. What happens
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-24
00:05 ---
One more thing we will fix a memory hog problem, if the source is correct
unlike PR 18634 which I get
errors on the mainline for.
--
What|Removed |Added
---
--- 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.
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-23
23:45 ---
The problem is the kernel is killing the process which generates the error
message, we cannot do
anything about it, this has been reported before.
--
What|Removed |Adde
