• 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: vincent habchi <email@hidden>
  • Date: Sun, 31 Jul 2011 08:39:51 +0200

> 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.

That is, of course, not true. When a process forks, the child and the parent, though being two separate processes, still share the same virtual memory map (at least until the child calls exec (3)). And you can arrange to share pages of memory in different processes via, e.g, shmat (2), at the Unix level. That's how most databases (e.g. PostGreSQL) work, inter alia.

Vincent_______________________________________________

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: Ron Hunsinger <email@hidden>
References: 
 >Return causes EXC_BAD_ACCESS (From: "Mr. Gecko" <email@hidden>)
 >Re: Return causes EXC_BAD_ACCESS (From: Graham Cox <email@hidden>)

  • Prev by Date: Re: Release build throw "unrecognized selector sent to instance" for a category method
  • Next by Date: Re: Return causes EXC_BAD_ACCESS
  • Previous by thread: Re: Return causes EXC_BAD_ACCESS
  • Next by thread: Re: Return causes EXC_BAD_ACCESS
  • Index(es):
    • Date
    • Thread