Re: guard malloc
Re: guard malloc
- Subject: Re: guard malloc
- From: "Wesley Smith" <email@hidden>
- Date: Mon, 26 May 2008 21:41:48 -0700
Sorry about the noise. The debugger log actually gives nice messages like:
If you really wanted to allocate so much memory, launch your
executable with the environment variable MALLOC_PERMIT_INSANE_REQUESTS
set to any value to circumvent this check.
Explicitly trapping into debugger!!!
wes
On Mon, May 26, 2008 at 9:35 PM, Wesley Smith <email@hidden> wrote:
> I was unable to find docs on this, but what does it mean when Guard
> Malloc triggers a SIGTRAP on a line that looks like:
>
> m_glVertices = new Vec3[cubesize*3*5];
>
> where cubesize is quite large ( > 500,000)? Is there a way to query
> why an error resulted?
>
> This is the tip of the stack:
> #0 0x9b5a27b8 in GMmalloc
> #1 0x90b4e5b3 in operator new
> #2 0x90b4e6a5 in operator new[]
>
>
> thanks,
> wes
>
_______________________________________________
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
| References: | |
| | >guard malloc (From: "Wesley Smith" <email@hidden>) |