Bug 26066 - XSlimmer breaks WebKit nightly builds
Summary: XSlimmer breaks WebKit nightly builds
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-28 13:16 PDT by Chris Latko
Modified: 2009-05-28 14:46 PDT (History)
1 user (show)

See Also:

Attachments
System Profiler report (deleted)
2009-05-28 13:20 PDT, Chris Latko 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Latko 2009-05-28 13:16:35 PDT 
WebKit Nightly (r44201) crashes when trying to load. I get the following from the console:

May 28 16:11:28 kabuto com.apple.launchd[216] ([0x0-0x36036].org.webkit.nightly.WebKit[9521]): posix_spawnp("/Applications/WebKit.app/Contents/MacOS/WebKit", ...): Bad CPU type in executable
May 28 16:11:28 kabuto com.apple.launchd[216] ([0x0-0x36036].org.webkit.nightly.WebKit[9521]): Exited with exit code: 1

Restarted machine and problem persists.
Comment 1 Chris Latko 2009-05-28 13:20:34 PDT 
Created attachment 30746 [details]
System Profiler report
Comment 2 Mark Rowe (bdash) 2009-05-28 14:18:47 PDT 
I can't reproduce this on my MacBook Pro running 10.5.7.  Can you please try downloading a fresh build from nightly.webkit.org and see whether you can reproduce this problem?
Comment 3 Chris Latko 2009-05-28 14:33:30 PDT 
Using a fresh version of r44201 works fine. Running Xslimmer on it, results in the launch failure.
Comment 4 Mark Rowe (bdash) 2009-05-28 14:35:42 PDT 
If you're going to modify an application it's probably not a great idea to file a bug report when your modifications break said application.
Comment 5 Chris Latko 2009-05-28 14:45:47 PDT 
My apologies.
Comment 6 Mark Rowe (bdash) 2009-05-28 14:46:57 PDT 
I logged a bug report with XSlimmer about this so hopefully others will not run in to the same issue.