Re: malloc causing vm_allocate errors
Re: malloc causing vm_allocate errors
- Subject: Re: malloc causing vm_allocate errors
- From: "Omar Awile" <email@hidden>
- Date: Wed, 4 Jul 2007 18:57:59 +0200
Boaah.. I feel so silly..
I compiled it as 64 bit code (on my linux system 64 bit is probably
the default setting for the used compilers) on darwin and it works!!!
I always thought that at least gcc had this somewhere in its default settings.
Thanks a lot.. So I guess the explenation is that it used more virtual
memory than can be addressed in 32 bit mode (at least on that system).
using 64 bit addressing resolves that issue of course...
Thanks again
omar
On 7/4/07, Jonas Maebe <email@hidden> wrote:
On 04 Jul 2007, at 18:12, Omar Awile wrote:
> 'top' is telling me about VM:
> VM: 3.90G + 7.19M 141826(0) pageins, 0(0) pageouts
> (my program is not running)
> So this means there should be by far enough memory around.
Those statistics are irrelevant. Every app gets its own VM space. If
your program is 64 bit clean, you can of course also always recompile
it as a 64 bit binary.
> I was not yet able to check with vmmap (or malloc_history) because my
> program spits out these error messages after a very short time and
> crashes right after.
"man malloc" also describes a number of environment variables you can
set.
Jonas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden