This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc behavior on memory exhaustion
- From: Andreas Schwab <schwab at suse dot de>
- To: Yuri Gribov <tetra2005 at gmail dot com>
- Cc: Andrew Haley <aph at redhat dot com>, Andrew Roberts <andrewm dot roberts at sky dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 09 Aug 2017 16:14:57 +0200
- Subject: Re: gcc behavior on memory exhaustion
- Authentication-results: sourceware.org; auth=none
- References: <951803b5-b5c8-67d4-c5cc-73dee3a267e3@sky.com> <91f1df6b-98ba-2df4-6404-e46692d4028f@redhat.com> <CAJOtW+4W2M7=uVoXsQ0Gudp9tMY1n0g70fPXNUEsm3sB6g5fxw@mail.gmail.com>
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."