diff options
| author | Kent Hansen <kent.hansen@nokia.com> | 2010-04-14 16:26:58 (GMT) |
|---|---|---|
| committer | Jason McDonald <jason.mcdonald@nokia.com> | 2010-05-04 00:17:33 (GMT) |
| commit | bb4690b7283f06036665fc1256754a4e8ac762c7 (patch) | |
| tree | f8c7e955128944e0baca7c3b305aa85f8c12a3f8 /examples | |
| parent | 8dc55ec51037d2603bff5492113887021c4174c3 (diff) | |
| download | Qt-bb4690b7283f06036665fc1256754a4e8ac762c7.zip Qt-bb4690b7283f06036665fc1256754a4e8ac762c7.tar.gz Qt-bb4690b7283f06036665fc1256754a4e8ac762c7.tar.bz2 | |
2010-04-14 Kent Hansen <kent.hansen@nokia.com>
Reviewed by Maciej Stachowiak.
Mac OS X: Use deployment target to determine whether memory tagging should be enabled
https://bugs.webkit.org/show_bug.cgi?id=34888
When building on (Snow) Leopard but targeting Tiger
(TARGETING_TIGER defined, BUILDING_ON_TIGER not defined),
WebKit would crash on Tiger because the tags passed to mmap
caused those function calls to fail.
Conversely, when building on Tiger but targeting Leopard
(BUILDING_ON_TIGER defined, TARGETING_LEOPARD defined), WebKit
would crash on Leopard because the tags passed to vm_map and
vm_allocate caused those function calls to fail.
Solution: Use TARGETING_TIGER rather than BUILDING_ON_TIGER to
govern the tag definitions. Use the same tags for vm_map and
vm_allocate regardless of target, since they work on
both. Fall back to the mmap tags that work on Tiger (that is,
"no tags") if targeting Tiger, since those tags also work on
Leopard.
* wtf/VMTags.h:
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@57583 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions