Re: large memory malloc
Re: large memory malloc
- Subject: Re: large memory malloc
- From: "James E. Hopper" <email@hidden>
- Date: Fri, 1 Jul 2005 07:57:08 -0400
nmap seems like what i want. i understand this is a brute force
method, but always before the images have been much smaller and it
was a quick and dirty tool. i just didnt want to rewrite the tool
for one pathological case. if there was a simple solution. since
there is not i will have to rewrite the app.
thanks for the info.
jim
On Jul 1, 2005, at 2:27 AM, Cameron Kerr wrote:
The amount of memory a user would be able to allocate is bounded by
a per-process (or per-user?) limit.
See ulimit(3) for more details.
It would be useful to know what malloc is returning. ie, what does
perror("malloc") print when malloc fails?
To allocate the amount requested, you may need to run as root.
But that is not really the problem. The problem is that your
problem domain is not a good mapping for your solution. You need to
break it down. As one poster suggested, mmap(2) may be a useful
solution.
If not, then you should segment the images and swap them in and out
as needed.
On 1/07/2005, at 12:32 PM, James E. Hopper wrote:
i have a simple xcode project that does a malloc that for the
latest data set has grown to just under 3gb. the malloc is
failing (on 10.3.9). since i have 4gb of ram and the docs imply i
can access up to 4gb space without having to go to 64 bit
addressing, i was hoping there was something simple i could do to
make this work?
--
Cameron Kerr
Telecommunications Teaching Fellow & SysAdmin
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden