From: Paul Sargent <Paul.Sargent@3dlabs.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2GB process crashing on 2.4.14
Date: Fri, 7 Dec 2001 14:15:43 +0000 [thread overview]
Message-ID: <20011207141543.G31161@3dlabs.com> (raw)
In-Reply-To: <20011207125821.D31161@3dlabs.com.suse.lists.linux.kernel> <E16CKrx-0005nL-00@the-village.bc.nu.suse.lists.linux.kernel> <20011207132317.E31161@3dlabs.com.suse.lists.linux.kernel> <p73k7vz6sc9.fsf@amdsim2.suse.de>
In-Reply-To: <p73k7vz6sc9.fsf@amdsim2.suse.de>
On Fri, Dec 07, 2001 at 03:02:46PM +0100, Andi Kleen wrote:
> Paul Sargent <Paul.Sargent@3dlabs.com> writes:
>
>
> > So if I was hitting this limit then I should see no / very few gaps, in the
> > /proc/<pid>/maps. Is that true?
>
> It usually fails when malloc() hits your libraries.
[remedies to increase available address space snipped]
> -Andi
>
> P.S.: I'm pretty sure this is a FAQ.
Yes, I think your right, this is. At least, I've come across it before, but
I'm not convinced this is my problem in this case.
I think it's failing about 1GB before getting to the bottom of the
libraries, but I'm going to monitor maps over the weekend to ensure it
doesn't start doing anything wacky just before crashing.
Paul
--
Paul Sargent
Tel: +44 (1784) 476669
Fax: +44 (1784) 470699
mailto: Paul.Sargent@3Dlabs.com
next prev parent reply other threads:[~2001-12-07 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011207125821.D31161@3dlabs.com.suse.lists.linux.kernel>
[not found] ` <E16CKrx-0005nL-00@the-village.bc.nu.suse.lists.linux.kernel>
[not found] ` <20011207132317.E31161@3dlabs.com.suse.lists.linux.kernel>
2001-12-07 14:02 ` 2GB process crashing on 2.4.14 Andi Kleen
2001-12-07 14:15 ` Paul Sargent [this message]
2001-12-07 12:58 Paul Sargent
2001-12-07 13:16 ` Alan Cox
2001-12-07 13:23 ` Paul Sargent
2001-12-07 13:48 ` Alan Cox
2001-12-07 14:01 ` Paul Sargent
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=20011207141543.G31161@3dlabs.com \
--to=paul.sargent@3dlabs.com \
--cc=ak@suse.de \
--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