Re: Linking problem (vm_alloc)
Re: Linking problem (vm_alloc)
- Subject: Re: Linking problem (vm_alloc)
- From: Bradley Flubacher <email@hidden>
- Date: Tue, 11 Dec 2007 09:43:40 -0500
Thanks,
I'm not explicitly specifying the linker data option- just using -g.
I believe that's producing stabs if I'm not mistaken.
I'm running on a Core Duo, so switching to 64-bit isn't an option
right now. If I knew that this would solve my problem, I wouldn't
mind having to upgrade, and I could justify it.
Brad
On Dec 11, 2007, at 9:39 AM, Shawn Erickson wrote:
On Dec 11, 2007, at 6:33 AM, Bradley Flubacher wrote:
While this seems like a large allocation, it should be doable even
with my 32-bit 10.4 installation.
That is a single allocation hence a contiguous virtual address
range must be available in the requesting processes address space.
It is likely that the virtual address space is fragmented enough
that no such range exists at the time of the allocation (the
requested amount if close to largest possible single allocation in
a perfectly clean VM address space of a typical 32b application on
Mac OS X).
You could try using the 64-bit version of the linker (think only
available on Leopard). Are you using DWARF? If not try using that
format (maybe try DWARD with dSYM).
-Shawn
_______________________________________________
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