Gotcha:<br><br>ktrace/kdump tells us that mmap() has<br><br>RET -1 12 Could not allocate memory<br><br>or that mmap returns ENOMEM. From mmap(2):<br><br> [ENOMEM] MAP_FIXED was specified and the addr argument was not
<br> available. MAP_ANON was specified and insufficient<br> memory was available. The system has reached the per-<br> process mmap limit specified in the
vm.max_proc_mmap<br> sysctl.<br><br>ogre% sysctl -a | grep vm.max_proc_mmap<br>vm.max_proc_mmap: 30645<br><br>and we are trying to allocate something around 92K. Why on earth there is such<br>a limit I don't know, but it is the culprit here. Now for a nice way to circumvent it
<br>apart from increasing it ;)<br><br><br><div><span class="gmail_quote">On 6/24/07, <b class="gmail_sendername">Jesper Louis Andersen</b> <<a href="mailto:jesper.louis.andersen@gmail.com">jesper.louis.andersen@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">ok, new hypothesis:<br><br>printing the right size of the pointer gives
<br><br>Couldn't map f7ff9954b0000000, 94208<br><br>etc. So I think this area is non-mappable for som reason. More investigation needed. <div><span class="e" id="q_1135ab3e6ced979c_1"><br></span></div></blockquote></div>
<br>