This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: mprotect() failed: Cannot allocate memory

From: PaweÅ Sikora <pluto at agmk dot net>
To: "Yann Droneaud" <yann at droneaud dot fr>
Cc: libc-help at sourceware dot org, "Mike Frysinger" <vapier at gentoo dot org>,linux-kernel at vger dot kernel dot org
Date: Wed, 21 Apr 2010 10:42:45 +0300
Subject: Re: mprotect() failed: Cannot allocate memory
References: <201004210105.20942.pluto@agmk.net><201004201917.23286.vapier@gentoo.org> <201004210144.18954.pluto@agmk.net><1271838139.28592.10.camel@localhost>

Dnia 21-04-2010 o 11:22:19 Yann Droneaud <yann@droneaud.fr> napisaÅ(a):

(...) mmap(NULL, 4896, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_ANONYMOUS, -1, 0) = 0x7f5fd97df000 mprotect(0x7f5fd97df000, 4096, PROT_NONE) = -1 ENOMEM (Cannot allocate memory)
Have you checked available memory on your system ? Or user limit ?
You test program is going to allocate
 79 + 1 pages for bm
 1 + 1 for each double arrays (x 40000)
So in the end your program is allocating 80080 pages, so about
312MBytes.
It not that big for a 64bits system.


afaics in gdb, the mprotect fails at i=32756. it's near to 2^15.
maybe some kernel data structures are full?

References:
- mprotect() failed: Cannot allocate memory
  - From: PaweÅ Sikora
- Re: mprotect() failed: Cannot allocate memory
  - From: Mike Frysinger
- Re: mprotect() failed: Cannot allocate memory
  - From: Paweł Sikora
- Re: mprotect() failed: Cannot allocate memory
  - From: Yann Droneaud

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]