Re: Increasing stacksize on Mac OSX

Hi Jared,
The stacksize is not the same as the amount of memory available to your program. The stacksize generally places a limit on the complexity and depth of the function calling tree. Space for data objects in NCL is taken what is usually called the "heap". There does seem to be a memory-related problem in your program but it may not have anything to do with not having enough memory. The message indicates some kind of corruption of the memory space. We may want to take a look at your code to see if we can duplicate the problem.
 -dave

On Jun 29, 2011, at 6:57 PM, Jared Lee wrote:

> I have 6 GB of memory on my Mac. I do believe that my script requires more memory than 64 MB. When I ran it on Linux systems I had unlimited stacksize and it ran without any problems.
>
> I came across this NCL for Mac page, which suggested making the stacksize unlimited. That should mean it's possible (unless whoever wrote this page never actually tried to do that themselves):
>
> http://www.ncl.ucar.edu/Download/macosx.shtml
>
> If I can't figure out how to increase the stacksize, that will likely cause me problems when I try to run WRF as well, because 64 MB is pretty darn small...
>
> Jared
>
>
> On Jun 29, 2011, at 6:47 PM, Dennis Shea wrote:
>
>> %> ulimit -s
>>
>> I think that the max stacksize for the MAC is 65532.
>> I don't think that there is an unlimited stacksize
>> like on many linux systems.
>>
>> ==
>> WHat is the available memory on your MAC? Does
>> your script require more memory then is available?
>>
>> On 6/29/11 6:35 PM, Jared Lee wrote:
>>> Hi, does anyone out there know how to increase the stacksize in Mac OSX (I'm running 10.6.8) beyond 65532 kB? I haven't been able to find a way to increase the stacksize to unlimited, or even anything larger than that. An NCL script that I have runs just fine on Linux systems, but when I run it on my new Mac, I get errors like this one:
>>>
>>> ==========
>>> ncl(47500) malloc: *** error for object 0x12c594c08: incorrect checksum for freed object - object was probably modified after being freed.
>>> *** set a breakpoint in malloc_error_break to debug
>>> sh: line 1: 47500 Abort trap
>>> ==========
>>>
>>> Because it's an mallloc error, I'm assuming that it'd go away if I could get the stacksize big enough, but OSX seems to make it hard or impossible to do that.
>>>
>>> Jared
>>>
>>> _______________________________________________
>>> ncl-talk mailing list
>>> List instructions, subscriber options, unsubscribe:
>>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk

_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Wed Jun 29 19:11:50 2011