• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Return causes EXC_BAD_ACCESS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Return causes EXC_BAD_ACCESS


  • Subject: Re: Return causes EXC_BAD_ACCESS
  • From: Graham Cox <email@hidden>
  • Date: Fri, 29 Jul 2011 11:15:24 +1000

On 29/07/2011, at 7:33 AM, 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.


No.

Memory is "virtual", the addresses you appear to be working with are not real (i.e. they don't refer to the real address of the physical RAM underneath). Instead, a bit of hardware translates these to the real addresses as needed at some level far below the perception of your program. You cannot access the virtual address space of any other process other than your own.

--Graham


_______________________________________________

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

  • Follow-Ups:
    • Re: Return causes EXC_BAD_ACCESS
      • From: vincent habchi <email@hidden>
References: 
 >Return causes EXC_BAD_ACCESS (From: "Mr. Gecko" <email@hidden>)

  • Prev by Date: Re: drawRect not getting called problem solved
  • Next by Date: Freaking out a bit...
  • Previous by thread: Re: Return causes EXC_BAD_ACCESS
  • Next by thread: Re: Return causes EXC_BAD_ACCESS
  • Index(es):
    • Date
    • Thread