From: Manfred Spraul <masp0008@stud.uni-sb.de>
To: saraniti@ece.iit.edu
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: weird calloc problem
Date: Thu, 18 Mar 1999 14:00:55 +0100 [thread overview]
Message-ID: <36F0F907.7A48D010@stud.uni-sb.de> (raw)
In-Reply-To: <Pine.LNX.3.95.990317180745.629A-100000@chaos.analogic.com>
On Tue, 9 Mar 1999 19:51:32 -0600 (EST), marco saraniti
<saraniti@neumann.ece.iit.edu> said:
> I'm having a calloc problem that made me waste three weeks, at this point
> I'm out of options, and I was wondering if this can be a kernel- or
> MM-related problem. Furthermore, the system is a relatively big machine and
> I'd like to share my experience with other people who are interested in
> using Linux for number crunching.
>
> The problem is trivial: calloc returns a NULL, even if there is a lot
> of free memory. Yes, both arguments of calloc are always > 0.
you wrote 'the system is a relatively big machine'.
Perhaps you have run out of virtual memory.
How much memory do you try to allocate? (more than 1 Gigabyte?)
How much physical memory do you have?
You Could also pause the process as soon as you calloc returns NULL
(i.e. if(ptr==NULL) while(1) { printf("error!!\n");} )
and look at the informations in /proc/<pid>. The file formats are
described in 'man proc'.
Regards,
Manfred
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-03-18 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-10 1:51 marco saraniti
1999-03-17 15:47 ` Stephen C. Tweedie
1999-03-17 23:12 ` Richard B. Johnson
1999-03-18 13:00 ` Manfred Spraul [this message]
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=36F0F907.7A48D010@stud.uni-sb.de \
--to=masp0008@stud.uni-sb.de \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=saraniti@ece.iit.edu \
/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