[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <op.vbh7tjp0zu3k57@pawels.alatek.krakow.pl>
Date: Wed, 21 Apr 2010 10:42:45 +0300
From: Paweł Sikora <pluto@...k.net>
To: "Yann Droneaud" <yann@...neaud.fr>
Cc: libc-help@...rceware.org, "Mike Frysinger" <vapier@...too.org>,
linux-kernel@...r.kernel.org
Subject: Re: mprotect() failed: Cannot allocate memory
Dnia 21-04-2010 o 11:22:19 Yann Droneaud <yann@...neaud.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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists