gcc behavior on memory exhaustion
Andreas Schwab
schwab@suse.de
Wed Aug 9 14:15:00 GMT 2017
On Aug 09 2017, Yuri Gribov <tetra2005@gmail.com> wrote:
> On Wed, Aug 9, 2017 at 2:49 PM, Andrew Haley <aph@redhat.com> wrote:
>> On 09/08/17 14:05, Andrew Roberts wrote:
>>> 2) It would be nice to see some sort of out of memory error, rather than
>>> just an ICE.
>>
>> There's nothing we can do: the kernel killed us. We can't emit any
>> message before we die. (killed) tells you that we were killed, but
>> we don't know who done it.
>
> Well, driver could check syslog...
The syslog is very system dependent and may not even be readable by
unprivileged users.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
More information about the Gcc
mailing list