Re: Return causes EXC_BAD_ACCESS
Re: Return causes EXC_BAD_ACCESS
- Subject: Re: Return causes EXC_BAD_ACCESS
- From: Scott Ribe <email@hidden>
- Date: Thu, 28 Jul 2011 16:10:30 -0600
On Jul 28, 2011, at 3:33 PM, Mr. Gecko wrote:
> From my understanding, this should happen when you, for an example, try to access the pointer 0x18c95b0 whenever that belongs to another process. However, I also thought that the Mac has a copy of memory space for each process and therefore should not be able to access memory that it doesn't own unless the core os does so.
No, not even close. It happens when you access a memory address that has not been mapped into your process' memory space. I've given you plenty of terms to google; go for it.
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden