[Webkit-unassigned] [Bug 35639] New: [Qt] mmap inside javascriptcore fails if building an app on os x >= 10.5 and deploying it onto 10.4
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Mar 3 03:22:50 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=35639
Summary: [Qt] mmap inside javascriptcore fails if building an
app on os x >= 10.5 and deploying it onto 10.4
Product: WebKit
Version: 528+ (Nightly build)
Platform: Other
OS/Version: Mac OS X 10.5
Status: NEW
Keywords: Qt
Severity: Normal
Priority: P2
Component: New Bugs
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: vestbo at webkit.org
This bug report originated from issue QTBUG-7065
http://bugreports.qt.nokia.com/browse/QTBUG-7065
--- Description ---
10% of my customers are still with os x 10.4!<br/>
Starting from Qt 4.6 mmaps are failing inside JavaScriptCore when I deploy an
application using QtScript compiled on OS X 10.6 onto 10.4.<br/>
I tracked down the issue to a platform detection mistake inside
src/3rdparty/javascriptcore/JavaScriptCore/wtf/Platform.h:
<p>.... about line 40 ...<br/>
...</p>
<p>The following small fix makes it work for me:</p>
<p>...<br/>
...</p>
<p>Also it should say "BUILDING_FOR_TIGER" instead of "BUILD_ON_TIGER" for the
sake of clarity.<br/>
PS: Thanks for having that flag to disable JIT. QtScript works just great for
me!</p>
--- Comments ---
We're aware of this issue (see http://www.pubbs.net/webkit/200909/85716).
Recently some macros were added to wtf/Platform.h, including TARGETING_TIGER (
= your BUILDING_FOR_TIGER).
I think the correct fix would be to use those defines in wtf/VMTags.h
(replacing BUILDING_ON_TIGER).
But it needs to be fixed upstream (http://bugs.webkit.org).
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list