From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: OOM strangeness
Date: 28 Aug 2002 15:45:37 +0200 [thread overview]
Message-ID: <yw1xptw3xfjy.fsf@fruxo.e.kth.se> (raw)
Yesterday I was compiling some things with gcc 3.1.1. When compiling
a rather large file with lots of optimizations, gcc was kill by the
OOM killer, even though I have 768 MB of ram and most of it was free.
Repeating the compilation succeeded. GCC did use ~250 MB or so, but
that shouldn't be a problem.
What could be causing this? A bug? Kernel version is 2.4.19-rc3 with
superpage patch on an Alpha 164SX system.
--
Måns Rullgård
mru@users.sf.net
reply other threads:[~2002-08-28 13:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xptw3xfjy.fsf@fruxo.e.kth.se \
--to=mru@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®