1. 10 Sep, 2013 1 commit
    • bmeurer@chromium.org's avatar
      Use PAGE_NOACCESS for guard pages in Windows. · 24a0cabd
      bmeurer@chromium.org authored
      Up until now we used PAGE_GUARD for guard pages in Windows, which
      will raise a STATUS_GUARD_PAGE_VIOLATION exception on first access
      and grant regular access afterwards. This behavior is required to
      implement automatic stack checking, or more generally to implement
      applications that monitor the growth of large dynamic data structures.
      
      However, this is not what we want for our guard pages, which are
      used as a security mechanism. What we really want is PAGE_NOACCESS
      here, which is the Windows-equivalent of PROT_NONE that we use on
      all other platforms.
      
      R=cdn@chromium.org
      
      Review URL: https://codereview.chromium.org/23458022
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16604 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      24a0cabd
  2. 09 Sep, 2013 17 commits
  3. 08 Sep, 2013 2 commits
  4. 06 Sep, 2013 15 commits
  5. 05 Sep, 2013 5 commits