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: Mike Frysinger <vapier at gentoo dot org>
To: libc-help at sourceware dot org
Cc: PaweÅ Sikora <pluto at agmk dot net>,linux-kernel at vger dot kernel dot org
Date: Tue, 20 Apr 2010 22:23:52 -0400
Subject: Re: mprotect() failed: Cannot allocate memory
References: <201004210105.20942.pluto@agmk.net> <201004201917.23286.vapier@gentoo.org> <201004210144.18954.pluto@agmk.net>

On Tuesday 20 April 2010 19:44:18 Paweł Sikora wrote:
> so, let's avoid EF and run following test:

good, the info is useful now

> mmap(NULL, 4896, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_ANONYMOUS, -1, 0) =
> 0x7f5fd97df000
> mprotect(0x7f5fd97df000, 4096, PROT_NONE) = -1 ENOMEM (Cannot allocate
> memory)

since you're using funcs that go straight to the kernel, this most likely isnt 
related to glibc at all, so sticking to LKML would be best.  the next step 
would be to look at the linux internals and find out why this is failing.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

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

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