On Wed, Jul 15, 2009 at 4:18 PM, Jens Alfke wrote:
>
> On Jul 15, 2009, at 3:50 PM, Albert J. Wong (王重傑) wrote:
>
>> Since you built it, you should be able to fire it up in a debugger and see
>> where it's dying. That's what I'd try first.
>
> More precisely:
> * Open chrome.xcodeproj
> * Make su
On Jul 15, 2009, at 3:50 PM, Albert J. Wong (王重傑) wrote:
> Since you built it, you should be able to fire it up in a debugger
> and see where it's dying. That's what I'd try first.
More precisely:
* Open chrome.xcodeproj
* Make sure the "chrome" executable is active
* Choose Run > Activate B
There may also be useful error messages in the error log (select
"Console" from the "Run" menu in Xcode).
--Amanda
On Wed, Jul 15, 2009 at 6:50 PM, Albert J. Wong
(王重傑) wrote:
> Since you built it, you should be able to fire it up in a debugger and see
> where it's dying. That's what I'd try f
Since you built it, you should be able to fire it up in a debugger and see
where it's dying. That's what I'd try first.
-A
On Wed, Jul 15, 2009 at 3:47 PM, n179911 wrote:
>
> Hi,
>
> I download the source of chromium and build successfully on MacOSX.
>
> When I start the TestShell.app, it launc
